Add TP 2.0 CCV and fees management

[krebernisak]

Token Pool 2.0: async GetCCVs / GetCCVsAndFees

TON-native replacement for EVM getRequiredCCVs + getFee

What. Adds the missing V2 CCV-management surface to the TON TokenPool, closing the headline gap in the EVM-parity. EVM exposes two sync view calls — getRequiredCCVs(...) (delegates to AdvancedPoolHooks) and getFee(...). TON can't use sync cross-contract views, so this lands a message/req-res translation.

Design (one round-trip, minimal).

• TokenPool_GetCCVs (0xc5476d2b) → TokenPool_CCVs (CCVs only; OffRamp).
• TokenPool_GetCCVsAndFees (0xd22944d5) → TokenPool_CCVsAndFees (CCVs and the pool-computed fee params in one reply; OnRamp). This bundles EVM's two calls into a single async round-trip.
• Both forward a shared TokenPool_GetCCVs to async advancedPoolHooks (replyTo=pool, context echoed back); the pool reassembles the correct reply variant from TokenPool_FeeContext (null → CCVs, else CCVsAndFees).
• Hook bounce finalizes via TokenPool_GetCCVsFailed (added TokenPool_GetCCVs to each pool's BouncedMessage with the same RichBounce handling as the other bounce paths).

Parity with TokenPool.sol. Exact port of getRequiredCCVs amount logic (outbound subtracts bps fee; inbound _calculateLocalAmount via parseRemoteDecimals(extraData)) and getFee (disabled/missing config → feesProvided=false → FeeQuoter defaults). Exposed both as on-chain messages and as a getCCVAmount GET for off-chain tooling.

Bindings & tests. Go (TON-SDK) message structs + GetCCVAmount getter + TLB registration + round-trip tests; generated TS wrappers; shared TokenPool.ccvFees.behavior.ts wired into all three concrete pools (LockRelease, BurnMint, LockReleaseLockbox) covering: empty-CCV reply + fwdPayload echo, post-fee math (enabled fee config), feesProvided=false (disabled config), revert on unsupported token/un-configured chain/disallowed finality, and the async-hooks path.

Notes. This is the pool-side mechanism only. TON V2 OnRamp/OffRamp consumers (OnRamp→GetCCVsAndFees, OffRamp→GetCCVs) intentionally land separately. Deviation from EVM: on-chain CCV queries revert for un-configured lanes/tokens (EVM's pure-view returns empty) so the async path fails loudly; off-chain tooling should probe via GET getters.