chore: implement compliance veda adapter

[MoMannn]

What?

• Variation of VedaAdapter to support Veda protocol with compliance extension

Why?

• To support premium money account vaults

How?

• By implementing extended veda protocol available here: incentive teller with principal checkpointing, IncentivePool, and rewards claiming Veda-Labs/boring-vault#627

Reference

Original Veda adapter: #166

---

Note

High Risk
New on-chain path moves user tokens and vault shares via publicly callable delegation redemption; safety depends on correct enforcer caveats and teller compliance checks.

Overview
Adds ComplianceVedaAdapter, a delegation-based bridge to compliance-enabled Veda tellers (Base V0.3 deposit API + yield-streaming withdraw). Deposits redeem a user→operator→adapter delegation chain, pull depositToken via ERC20TransferAmountEnforcer terms on the leaf caveat, then call teller.deposit with backend ComplianceData so shares mint to the root delegator with signatures bound to the adapter as caller. Withdrawals follow the same pattern with vault shares and are not compliance-gated.

Also ships IComplianceVedaTeller, a CREATE2 DeployComplianceVedaAdapter script (with notes on Monad simulation quirks), and Monad fork tests covering adapter/batch flows plus compliance replay, expiry, signer, and slippage failures. CI and .env.example now wire MONAD_RPC_URL through Infura for those tests.

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