fix: add liquidity example

[mkflow27]

This pr fixes the add-liquidity-example. The following changes were made:

• replace the api endpoint. Some V3 pools are not part of the production api endpoint. At a further point in time we need to change it back to the production endpoint
• Reduce add liquidity amount as otherwise the priceImpact calculation (swap queries) will revert with the pool used, due to revert MaxAmountInRatio
• Add the chain parameter to the api query
• Added chain name strings the api requires to constants. I initially tried accessing the Chain.name from https://github.com/wevm/viem/blob/main/src/types/chain.ts#L49. However, even with uppercasing them they do not perfectly match with what the api expects.

[johngrantuk]

@brunoguerios - "Reduce add liquidity amount as otherwise the priceImpact calculation (swap queries) will revert with the pool used, due to revert MaxAmountInRatio" - is that a bug in priceImpact?

[johngrantuk]

I didn't realise the API had changed to require the chain field. Seems nicely handled 👍

[johngrantuk]

LGTM and runs locally.

[mkflow27]

I tried to simulate the query on tenderly and it reverted. https://dashboard.tenderly.co/mcquardt/project/simulator/a4c4577e-ab88-44c9-88e9-244a97e9450f?trace=0.1.0.2.2.0.7.3 numbers I used were from a debugging run

[brunoguerios]

@brunoguerios - "Reduce add liquidity amount as otherwise the priceImpact calculation (swap queries) will revert with the pool used, due to revert MaxAmountInRatio" - is that a bug in priceImpact?

Price Impact calculation for Add Liquidity Unbalanced relies on swap queries under the hood and if they are too large compared to pool balances, they will revert due to MaxAmountInRatio.

[johngrantuk]

@brunoguerios - any further comments before this gets merged?

[brunoguerios]

LGTM ✅