Correct vaa-payload-parser to set the actual destination chain for gateway transfers

[M-Picco]

It can be extracted from the parsed VAA payload.

We need to analyze the impact on analytics/metrics beforehand, since everything is nested under the wormchain id (3104)

We can't do it for VAAs with gateway as a source since we don't have access to the information on the VAA. The only way to do it would be to query the DB (which may not yield a result since the tx-tracker runs in parallel to the parser; although we may analyze the idea of changing the sequence and providing the tx to the parser request) or query the rpcs, which is not ideal.

This may also require a backfiller to recreate the influx collection