feat(cct-sdk): Add deploy evm token pool + version resolution

[apedrob]

What

• Add deployTokenPool to EVMTokenManager (build + execute): deploys a TokenPool at 2.0.0, type selects the contract (BurnMintTokenPool, BurnFromMintTokenPool, BurnWithFromMintTokenPool, LockReleaseTokenPool)
  • generateUnsignedDeployTokenPool for offline/multisig; deployTokenPool signs + submits, returns { hash, contractAddress }
• Add resolveTokenPool: read onchain typeAndVersion, narrow to a known pool type + version
• transferOwnership resolves the pool's real type/version to pick the ABI and floor-match the encoder (was a hardcoded interface)
• Slim version file to the version/resolution axis; move deploy artifacts (creation-bytecode map + DeployableTokenPoolType) next to the deploy op

Why

• CCT needs first-class pool deployment to complete the 2.0.0 pool deployment
• Resolving type/version on-chain keeps encoder/ABI selection correct as pool versions evolve

Testing

• CI for deployTokenPool (golden-vector init-code per type incl. lockBox, param validation, execute paths)
• transferOwnership probe + version-resolution tests; full CCT suite green, typecheck + lint clean

[vercel]

You must have Developer access to commit code to Chainlink Labs on Vercel. If you contact an administrator and receive Developer access, commit again to see your changes.

Learn more: https://vercel.com/docs/accounts/team-members-and-roles/access-roles#team-level-roles

[mervin-link]

Nit: Since we are resolving transferOwnership to token pool interface, maybe it's better to rename it specific to token pool. But it's not a blocker.

[aelmanaa]

Re-checked at fa96c23.

The previous lockBox correctness issue is fixed:

• LockRelease now requires lockBox
• zero lockBox is rejected early

Remaining lockbox gap (still blocking for me):
LockRelease is not fully exercisable end-to-end through SDK-only operations.

What is missing:

1. No deployLockBox operation to create the required lockbox from the SDK flow
2. No documented lockbox caller-authorization step before pool usage

Please resolve with one of these paths:

• Preferred: add deployLockBox and document the full LockRelease sequence including authorization
• Alternative: explicitly scope LockRelease as partial in this PR and link a follow-up issue in PR description and docs

[aelmanaa]

The LockRelease deployTokenPool example still omits lockBox.
Please include lockBox in the example so copy-paste usage compiles and matches runtime requirements.