`_handleAdditionalPayload` is not called when releasing inbound rate limited transfers on EVM

[djb15]

In the EVM implementation the NTT Manager _handleTransfer() function calls _handleAdditionalPayload() only on the non-queued code path. When a transfer hits the inbound rate limit and is queued via _enqueueInboundTransfer(), _handleAdditionalPayload() is never called — neither at queue time nor at completion time. Any NTT integrator that uses _handleAdditionalPayload() doing extra/custom processing on receipt would have that logic silently skipped for every rate-limited transfer. Any address can call the permissionless completeInboundQueuedTransfer() to force delivery, bypassing the integrator's hook entirely.

Any integrators requiring the use of _handleAdditionalPayload() for critical accounting or processing should avoid using inbound rate limiting.

[mdulin2]

This is slightly non-trivial to fix, especially if we want to maintain backwards compatibility. Only the recipient, and amount are stored in the queued transfer. _handleAdditionalPayload() needs the source chain, source ntt manager address, message ID, message sender, and the whole nativeTransferToken information with decimals, and amount inside of it. So, more data would have to be put into the struct InboundQueuedTransfer.