remote state downloading and usage in gno run|test

[0xtekgrinder]

Description

One of the issue I encountered when developing autoswap realms is that It depend heavely on gnoswap realms and to make accurate tests I need to mock the entirety of the project.

This is difficult and can lead to error in the mocking process causing issue later on when deploying.

To fix this issue, we could try to implement a fork process when running tests so that instead of fetching the realms state from the local vm, it could reach out to an provided rpc and make the calls directly.

[thehowl]

I believe we had an issue somewhere about downloading the state, but it's something we had also discussed in relation to gnodev. (cc/ @gfanton)

I'm not sure how we can have it in a way that makes sense. I think that we should have if anything a way to download a remote state into a file, which can be understood by gno test - this way you have a gnokey download and a gno test -state=file as two separate commands. (It means also that the test part is deterministic and not dependent on a changing remote state).

We should not have gno test work directly with a remote state as you suggest, though.

Related #2376