Fix test failing intermittently

[brunoguerios]

• Fix Add Liquidity Boosted Integration test that was intermittently failing on CI

Also:
Closes #565

[brunoguerios]

Main change: adapt anvil fork to mine blocks every 1 second, instead of default behavior of instant auto-mine after every transaction.

Worth noting that this caused issues with how we read balances to check for success. Apparently getBalance reads are applied to the last block mined, so we need to wait for confirmation of the token balance setup (i.e. stataUSDT minting on this specific test) in order to properly read balances and assert results.

Also, apparently snapshot doesn't work well with these time based blocks, so these tests are "incremental" in the sense that they run one after the other in the same local fork.

[MattPereira]

I think this is just problem with my machine that I will investigate, but wanted to report just in case

For some reason takes more than twice as long for me to run locally vs the GHA

[MattPereira]

@brunoguerios Fantastic job hunting down the solution for this one! 🎉

Will be so nice to not have to re-run the tests for future PRs / releases 😌

[mkflow27]

Great changes Bruno.

[mkflow27]

I think this is just problem with my machine that I will investigate, but wanted to report just in case

For some reason takes more than twice as long for me to run locally vs the GHA

Same for me.

This error has happened a few times before on my machine as well but for different files.

[johngrantuk]

Remove this comment

[brunoguerios]

I'm tracking down the source of the issue here. Apparently the issue lies in the fallBackRpc url, because the one I have set on .env is working as expected. I'll fix that over here.

[brunoguerios]

Sharing what I found so you're aware:

attempting to fetch an env var as process.env[<<key>>] for a non existing key will sometimes return undefined and sometimes 'undefined' as string - we have to check both cases before deciding to use the fallBackRpc