feat(sdk)!: add scoped authentication key SDK support

[PastaPastaPasta]

Issue being fixed or feature implemented

Applications and wallets must preserve the scoped key permissions enforced by #4613. This PR is stacked on feat/scoped-contract-auth-keys (#4613) and contains the SDK changes only.

What was done?

• Add native scope ABI fields, marshalling, cleanup, restore, and JNI transport; replace the foundation PR’s unsupported-scope guard with complete scope support.
• Preserve scopes in Kotlin persistence (Room 11→12), Swift wrappers/key refresh, and WASM construction and serialization APIs.
• Freeze the V4 SwiftData relationship component and migrate V4→V5 instead of changing V4’s checksum. Existing wallet/key relationships and Keychain references survive, and scope bytes persist across reopening.
• Add the application integration guide and SDK regression/smoke coverage.

How Has This Been Tested?

• Built the macOS native framework and Swift package locally.
• All 7 SwiftData migration tests passed, including V4→V5 preservation and durable scope storage.
• Verified the complete stacked tree is identical to the original feat(platform)!: add contract-scoped authentication keys #4613 head plus the SwiftData migration fix.
• Original Kotlin/JNI/WASM changes and their tests are preserved from feat(platform)!: add contract-scoped authentication keys #4613; CI will validate the split branches.

Breaking Changes

Native libraries, generated headers, and Swift/Kotlin consumers must update together because public-key FFI layouts gain scope fields. Existing stores migrate with Room 11→12 and SwiftData V4→V5. Merge #4613 first; protocol-14 activation is required to register/use scoped keys.

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have added "!" to the title and described breaking changes in the corresponding section if my code contains any
• I have made corresponding changes to the documentation if needed

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 0eb6619e-26a6-4a23-ba4e-228f1acfcc5a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[thepastaclaw]

🕓 Queued for automated review — 7th in line, estimated start in ~1.4 h (commit c519d1b)
Estimated review time once started: ~25 min (two-phase automated review; median of recent runs).

• Request priority review — tick this box and the review moves to the front of the queue.