[adapter-stellar] grant_role/revoke_role argument order is pinned to stellar-contracts v0.5.x — breaks against >= v0.6.0

Summary

buildGrantRoleTransaction and buildRevokeRoleTransaction in packages/adapter-stellar/src/access-control/actions.ts send arguments in the order (caller, account, role):

• https://github.com/OpenZeppelin/openzeppelin-adapters/blob/6c9f72e7fac3844d02d3d7d0f3256b0c4d0335c6/packages/adapter-stellar/src/access-control/actions.ts#L52-L54
• https://github.com/OpenZeppelin/openzeppelin-adapters/blob/6c9f72e7fac3844d02d3d7d0f3256b0c4d0335c6/packages/adapter-stellar/src/access-control/actions.ts#L89-L91

That matches stellar-contracts v0.5.x. Since v0.6.0 (PR #495, "inconsistencies across mint and caller") the trait is grant_role(account, role, caller) / revoke_role(account, role, caller) — unchanged through v0.7.2 (current latest) and v0.8.0-rc.3:

• v0.5.0: https://github.com/OpenZeppelin/stellar-contracts/blob/v0.5.0/packages/access/src/access_control/mod.rs#L183
• v0.7.2: https://github.com/OpenZeppelin/stellar-contracts/blob/v0.7.2/packages/access/src/access_control/mod.rs#L214

Args are passed positionally (contract.call(functionName, ...scValArgs)), so against any contract built on stellar-contracts ≥ 0.6.0 the host receives an Address where a Symbol is expected and simulation fails. Every grant/revoke attempted from Role Manager against a current OZ contract errors out. Detection, role listing, enumeration and the two-step admin/ownership transfers are unaffected (their signatures didn't change).

Reproduction

Live testnet contract built on stellar-access =0.7.2: CBLPZP7LTLJOBDDHVNDOGGIMQIJEA4EQFN3E7LVBRJSR6E4NOMNJPNES (deploy tx: https://stellar.expert/explorer/testnet/tx/d7b2c28c80654a46153fbea131935dd4db861bdb8a54a2a3401bbff3d8cd86ad)

1. Add the contract in Role Manager (Stellar Testnet) — detection and role listing work (role compliance visible).
2. Attempt Assign role (or revoke) with any wallet:

HostError: Error(WasmVm, InvalidAction)
data: ["VM call trapped: UnreachableCodeReached", grant_role]
fn_call data: [G... (Address), G... (Address), "compliance" (Symbol)]   <-- v0.5 order

3. Simulating the same call with the current order (account: Address, role: Symbol, caller: Address) via stellar-sdk succeeds — the contract itself is fine.

Suggested fix

Reorder args/argTypes in both builders to (account, role, caller):

functionName: 'grant_role',
args: [account, roleId, caller],
argTypes: ['Address', 'Symbol', 'Address'],

Same for revoke_role. If supporting v0.5.x contracts still matters, the arg order could be derived from the contract spec (the loader already parses it) instead of being hardcoded.

Happy to open a PR for this.

Environment

• @openzeppelin/adapter-stellar 2.2.0 (bug present in the published dist), consumed by Role Manager ^2.2.0
• Hosted app: https://rolemanager.openzeppelin.com, Stellar Testnet
• Contract library: stellar-access =0.7.2, soroban-sdk 26.x

Start in packages/adapter-stellar/src/access-control/actions.ts and inspect buildGrantRoleTransaction and buildRevokeRoleTransaction, along with how their positional args and argTypes are assembled. Done means both builders work with stellar-contracts v0.6.0 and later while preserving the unaffected access-control operations; use the provided Stellar testnet reproduction to verify grant and revoke simulation.