promote to prod

[mendesfabio]

Description

• add rETH and weETH to pricing assets #572
• add event emitter to optimism #574
• Multiple Quote Tokens support for FXPools: FXPoolDeployerTracker #575

We had an issue with graph-node (graphprotocol/graph-node#5308) which delayed this release.

I've done a few commits to dev to organize everything but TLDR the plan is: we're promoting the staging pruned version to both production endpoints -prune set to last 1.5M blocks = 1 month. The only service we know that does time-travel queries is Snapshot and a month of data is more than enough for them - we've done this same thing in the past as a workaround for another issue and didn't have any trouble.

Actually, Polygon unpruned has been syncing quite fast so I don't think we have to promote the pruned version to both production endpoints. @danielmkm if you can leave an approval here I will only merge when Polygon unpruned is synced which should happen by the end of my day.

Besides, GH actions for building and linting are expected to fail - this PR bumps the Node version and should fix it.

How should this be tested?

• Querying all FX pools on Polygon returns both:
  • SBC / USDC.e: created with the previous/existing FXPoolDeployer contract
  • XSGD / USDC : created with a new FXPoolDeployer contract

dev -> master

• I have checked that all beta deployments have synced
• I have checked that the earliest block in the polygon pruned deployment is 55300515, Mar-31-2024 09:18:32 PM
  • The earliest block is more than 1 day old
• I have checked that core metrics are the same in the beta and production deployments

[danielmkm]

Love the detailed and clear writeup and testing instructions. Looks good!