fix(client): clean up deposit wallet deployment

[cesarenaldi]

Summary

• Clean up secure client Deposit Wallet resolution after the beacon factory upgrade
• Preserve deployed legacy UUPS Deposit Wallets when wallet is omitted
• Default new Deposit Wallet deployments to beacon wallets without runtime factory probing
• Apply the behavior consistently for sync and async clients

Verification

• uv run pytest tests/unit/test_client.py
• uv run ruff check .
• uv run ruff format --check .
• uv run pyright
• uv run pytest -m "not integration"

---

Note

Medium Risk
Changes which on-chain address clients bind to at creation and deploy time; wrong resolution could mis-route funds or deploy the wrong wallet type, though behavior is covered by new unit tests.

Overview
Updates default Deposit Wallet resolution when wallet is omitted on sync and async secure clients, replacing on-chain factory probing with a relayer-backed legacy check plus deterministic beacon derivation.

When no wallet is passed, the client derives the legacy UUPS address and asks the relayer whether that wallet is already deployed; if yes, it keeps using the legacy address so existing users are unchanged. If not, it defaults to the beacon Deposit Wallet address for new deployments.

Deploy-on-create (_deploy_default_deposit_wallet) now expects the resolved wallet to match the beacon-derived address only—no RPC derive_current_deposit_wallet_* calls in the client path.

Unit tests cover both branches (legacy deployed vs beacon default) for SecureClient and AsyncSecureClient.

^{Reviewed by Cursor Bugbot for commit c098c9b. Bugbot is set up for automated code reviews on this repo. Configure here.}