[E2E - Upgrade Testing] switch e2e test setup to creating genesis and configs via Dockertest

[p0mvn]

Background

This is part of #1235 epic

The preceding tasks include #1293 and #1330. This issue is blocked on these being merged.

Assuming that both are merged, we should be able to initialize genesis and config data via:

docker run -v < path >:/tmp/osmo-test osmosis-e2e-chain-init:debug --data-dir=/tmp/osmo-test
All chain data is placed at the given < path > that is mounted as a volume on the container. In addition, this PR introduces documentation about the current state of the e2e tests.

For the next step, we need to convert func (s *IntegrationTestSuite) configureChain(chainId string) in e2e_setup_test.go to initialize genesis and configs via Dockertest by using the newly created osmosis-e2e-chain-init:debug and mount its output on a volume.

Then, we should mount osmosis:debug containers that run validators on these mounted configs.

Please note that currently the chain id in the script used by the osmosis-e2e-chain-init:debug container is hardcoded. Instead, it should be passed to the container via Dockertest and read from the script as a flag.

Acceptance Criteria

• chain initialization in e2e tests uses Dockertest and the osmosis-e2e-chain-init:debug container
• e2e tests continue to pass