feat: migrate ready to the hub

[arlert-armin]

Summary

This PR migrates Ready to the Hub and introduces Starknet namespace support in the core.
The migration required updating Ready’s connection flow to align with the Hub architecture, but no blockers or limitations were encountered. Starknet namespace integration was added cleanly, with no breaking changes to existing flows.

Key changes:

• Migrated Ready to use the Hub connection and capability model.
• Added Starknet namespace implementation to the core.

No known limitations were found.

Related PRs:

#1325

Fixes # (issue)

How did you test this change?

I validated the new implementation across both Ready and Starknet flows:

• Confirmed Ready connects successfully via the Hub with expected behavior.

• Verified Starknet namespace resolution, connection, and account retrieval.

• Test A

• Test B

---

Checklist:

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• Implemented a user interface (UI) change, referencing our Figma design to ensure pixel-perfect precision.