feat(sdk): add pre-send destination-liquidity preflight that mandatorily simulates the destination pool's releaseOrMint for token transfers

[aelmanaa]

This pull request introduces significant improvements to the gas estimation documentation and SDK, particularly around pre-send validation and error handling for CCIP transfers. The main focus is on clarifying and enhancing how estimateReceiveExecution not only estimates gas but also validates transfer executability on the destination chain, helping developers avoid stuck transfers. Additionally, new error types and lower-level simulation primitives are documented and implemented, and the guides are reorganized to highlight these features.

Documentation and Guide Improvements:

• Added a new guide, pre-send-validation.mdx, detailing how estimateReceiveExecution validates that a transfer can execute on the destination chain before sending, including error handling and lower-level simulation primitives.
• Updated gas-estimation.mdx to clarify that on EVM chains, estimateReceiveExecution simulates ccipReceive and returns gas units, while on Solana it estimates compute units; also documented that the method validates executability and throws errors if the transfer would be stuck. [1] [2]
• Improved tables and descriptions in gas-estimation.mdx for consistency and clarity, including error and method reference tables. [1] [2] [3]
• Added the new "Pre-Send Validation" guide to the SDK sidebar for better discoverability.

SDK and Error Handling Enhancements:

• Introduced new error codes and exports for destination pool preflight checks: CCIPDestExecutionRevertError and CCIPDestSimulationUnavailableError, improving error reporting when a transfer would fail on the destination. [1] [2]
• Extended the Chain class with a new simulateLockOrBurn method, allowing simulation of source pool logic to obtain accurate data for destination pool validation.
• Updated the validation logic in the SDK to allow more flexible message input and removed redundant liquidity checks from the chain-level preflight, as these are now handled by destination simulation. [1] [2] [3]

[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

[andrevmatos]

Prefer code as doc:

Suggested change

	export const CCIP_POOL_V1_INTERFACE_ID = '0xaff2afbf'
	export const CCIP_POOL_V1_INTERFACE_ID = id('CCIP_POOL_V1').substring(0, 10) as '0xaff2afbf'

[andrevmatos]

I don't think you need a fork.test for these; fork tests are mostly for read-write tests; your simulations here are read-only, a plain integration test would do