feat: migrate clover to the hub

[arlert-armin]

Summary

This PR migrates Clover to the Hub and adds the required adjustments to support its unique connection behavior.
Clover’s implementation differs from standard Solana providers, so a custom connection action was added to properly handle its flow.

Currently, Clover has known issues with signing on both EVM and Solana—it cannot sign transactions on either network. These issues originate from Clover itself and are not caused by the Hub integration. All connection-related logic functions correctly.

Additional adjustments:

• Implemented a custom connect action to support Clover’s non-standard Solana connection flow.
• Updated account switching behavior to rely on EVM provider events, fetching accounts on each event to stay in sync.

Fixes # (issue)

---

How did you test this change?

I tested Clover’s behavior under the Hub integration to validate connection and account management:

• Verified that the custom connection action correctly initializes the Clover provider.

• Confirmed EVM instance events trigger account changes and that accounts are refreshed on each event.

• Tested connection for both EVM and Solana flows.

• Attempted signatures on both EVM and Solana (expectedly failed due to existing Clover limitation).

• 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.