[Epic] Testnet / Chain upgrade flow automation (Sprint 6)

[ValarDragon]

The goal of this epic, is to reduce the time taken to produce testnets, and test items in an upgrade. There is a never ending list of items we could add to these, but this Epic should be focused on things we would like to add near-term, to provide the biggest speedups for our workflows.

• [E2E] Create e2e test set up #1416
• [E2E - Upgrade Testing] Add CI pipelines to test upgrades and chain integrity post-upgrade #1235
• [Import Genesis] Speeding up the import genesis time #1413

[p0mvn]

CI tests of upgrade succeeding, and basic properties being preserved post-upgrade
This can likely be done via starport
Basic properties we can test are:
Send txs still working
Pool swaps working with expected values
IBC sends still work on existing channels
IBC channel client/creation still works

@ValarDragon is this related to e2e tests? Do you think I could move this to #1202 ?

[niccoloraspa]

As mentioned in the last call and my @p0mvn I think we should split this in two.

1. E2E test where the only task left would be to identify and write more tests
2. Chain upgrade tests ~ tracked here: [E2E - Upgrade Testing] Add CI pipelines to test upgrades and chain integrity post-upgrade #1235

[ValarDragon]

Some goals brought up on call: Identify, make issues for, and write test cases for most important end to end tests.

(More specifically for upgrades!)

Can we improve the framework to allow more messages to get executed in the "Old version" code?

Can we have varied full nodes configurations that "follow" the upgrade process.

[czarcas7ic]

As per chain dev call today, moving issues/tracking to infra where most of the work on this is being done