test(e2e): improve stateful e2e testing

[lumtis]

Description

• Make stateful e2e testing directly with one Makefile command without manual interaction
• Replace zetavisor with cosmovisor for the test

To perform the upgrade test, run:

make stateful-upgrade-source
cd contrib/localnet
docker-compose logs orchestrator -f

This start the chain with v11, send a upgrade proposal to current source at 200, run smoke tests, rerun smoke tests after upgrade and client restart.

For V11, a specific branch v11.0.0-patch-core-params is used to patch the hardcoded deployed contract addresses on local goerli since these values have changed after smoke tests revamp.

We will have to update the script each time to test with the next version for upgrade.

Note: seems there is an issue with the core params refactoring: e6ccc5be11ab9a18ea4a9f68519f89bc5bd21212
The upgrade test passes before this PR

[github-actions]

!!!WARNING!!!
nosec detected in the following files: contrib/localnet/orchestrator/smoketest/config/config.go

Be very careful about using #nosec in code. It can be a quick way to suppress security warnings and move forward with development, it should be employed with caution. Suppressing warnings with #nosec can hide potentially serious vulnerabilities. Only use #nosec when you're absolutely certain that the security issue is either a false positive or has been mitigated in another way.

Only suppress a single rule (or a specific set of rules) within a section of code, while continuing to scan for other problems. To do this, you can list the rule(s) to be suppressed within the #nosec annotation, e.g: /* #nosec G401 */ or //#nosec G201 G202 G203
Broad #nosec annotations should be avoided, as they can hide other vulnerabilities. The CI will block you from merging this PR until you remove #nosec annotations that do not target specific rules.

Pay extra attention to the way #nosec is being used in the files listed above.

[ws4charlie]

looks nice