Update RWA SEP

[ozgunozerk]

Summary

After @janewang noticed we are missing recovery_target from this SEP, I've taken a deeper look to see if there are other discrepancies left. And yes, there were some :)

Changes

• Added token: Address to all five hooks (can_transfer, can_create, transferred, created, destroyed) — required for a single compliance contract to serve multiple RWA tokens with per-token state. Also updated the simplified can_transfer snippet in the Architecture Overview.
• Added the two getters that already exist in the impl: get_modules_for_hook and is_module_registered.
• IdentityVerifier: added recovery_target(e, old_account) -> Option<Address>. RWAToken::recover_balance calls into this to confirm an identity recovery has already happened before moving balances.
• IdentityRegistryStorage: replaced the associated-type type CountryData: FromVal<Env, Val> with Vec<Val> parameters, and added a note explaining the Soroban SDK constraint (#[contractclient] cannot derive on traits with associated types) that drives this choice.
• Renamed the recovery event Recovery → RecoverySuccess to match the impl.
• Dropped the operator topic from AddressFrozen (impl emits only user_address and is_frozen).

[Copilot]

Pull request overview

This PR updates SEP-0057 (T-REX / RWA token standard) to better align the written specification with the referenced implementation, especially around compliance hooks, recovery flows, and identity registry/country data interfaces.

Changes:

• Extend compliance hooks to include token: Address, and add missing compliance getters (get_modules_for_hook, is_module_registered).
• Add IdentityVerifier::recovery_target(...), add the missing CountryDataManager trait, and switch country-data trait parameters to Val-based shapes.
• Align event specifications with the implementation (rename Recovery → RecoverySuccess, and remove operator from AddressFrozen topics).

[ozgunozerk]

Prettier check is failing due to sep 23, not this one

[janewang]

Adding @mootz12 and @marcelosalloum for visibility

[leighmcculloch]

This change updates a draft SEP without changing its version or changelog. Can those be updated?

[leighmcculloch]

@ozgunozerk It's common for SEPs to update their version, in this case:

Suggested change

	Version: 0.1.0
	Version: 0.2.0

And to also note what changed in the changelog at the very bottom of the SEP:

stellar-protocol/ecosystem/sep-0057.md

Lines 1416 to 1418 in bcc47c2

	## Changelog
	- `v0.1.0` - Initial draft