chore: gut vibecoded miden-rpc-proxy lib (supplanted by miden-agglayer)

[revitteth]

Summary

Kurtosis already deploys `gateway-fm/miden-agglayer` as the miden-proxy service (commit `e7b4660`). The lib + main + bins in `src/` were the prior vibecoded implementation, dead code since the supplant, and stopped compiling against current `miden-client` (API drift on `Felt::as_int`, `OutputNote::Full`, `create_agglayer_faucet` signature, etc.).

This PR removes the dead code so the repo can build cleanly and reflects what's actually deployed.

Removed

• `src/main.rs` + the `miden-rpc-proxy` binary.
• `src/{address_mapper,agglayer_faucet,asset_mapping,block_state,claim_tracker,client,config,decode,error,log_synthesis,receipt,storage,types}.rs` — vibecoded modules; equivalents live in `gateway-fm/miden-agglayer`.
• `src/bin/{verify_notes,claim_note}.rs` — operator helpers, drifted off miden-client v0.14.4.
• `examples/gen_signed_tx.rs` — same drift class.

Kept

• `tests/phase{1,2,3}.rs` + `tests/common` — miden-client integration tests (no proxy involvement). They have their own API drift vs v0.14.4; that's a separate fix.
• `kurtosis/miden-cdk/` — the Starlark package that deploys miden-agglayer + aggkit + bridge-service + agglayer + miden-node.
• `scripts/` — operator/test harnesses driving the Kurtosis stack.

Cargo.toml realignment

• Pin `miden-client` to `tag = "v0.14.4"` (was `branch = "agglayer-integration-tests"`) — same pin as `gateway-fm/miden-agglayer`. Bumping these MUST stay in lockstep or `sync_transactions` fails with `invalid wire type` decode loops.
• Drop unused deps (jsonrpsee, tower, alloy, etc.) — none of the surviving code uses them.

Validation

• `cargo check` — green ✓
• Tests still need an API port to v0.14.4 (separate scope; not blocking the supplant).

Follow-up

• Port `tests/phase{1,2,3}.rs` to miden-client v0.14.4 API (`build_consume_notes` now takes `Vec`, etc.).
• Run `scripts/e2e-kurtosis.sh` against the RD-862-patched `miden-agglayer` image to validate the full e2e flow.
• Once `fix(rd-862): close GER decomposition race via aggkit two-root mode gateway-fm/miden-agglayer#37` and `feat(aggoracle): add UseUpdateExitRoot mode to forward both exit roots agglayer/aggkit#1597` merge and tagged releases ship, swap the kurtosis package's image refs to public tags.

🤖 Generated with Claude Code

[revitteth]

@mandrigin — careful review appreciated when you're around. Two related changes here:

1. Gut the vibecoded miden-rpc-proxy lib in src/ — it's been dead code since commit e7b4660 made the kurtosis package deploy gateway-fm/miden-agglayer instead, and it stopped compiling against current miden-client v0.14.4 (Felt::as_int, OutputNote::Full, create_agglayer_faucet arity all drifted). tests/phase{1,2,3}.rs are kept (they don't depend on the lib) but they have their own API drift to v0.14.4 that's out of scope here.

2. Plumb the RD-862 fix through the kurtosis package — fixtures/aggkit-config.toml style UseUpdateExitRoot = true in the inlined aggkit config template, aggkit_image pinned to the patched build in params.yaml, and the missing migrations/002_faucet_registry.sql appended to the inlined migration SQL (proxy startup was failing with relation "faucet_registry" does not exist).

Validated: scripts/e2e-kurtosis.sh --fresh deploys all services healthy, aggkit logs EVMChainGERSender initialized in direct_update_exit_root mode, and N=30 0ms-gap burst against the kurtosis ports gives 30/30 deposits ready_for_claim with 0 orphan GERs. Linked PRs: gateway-fm/miden-agglayer#37 and agglayer/aggkit#1597.