Refactor/act test env setup

[Yaiba]

This pr makes acceptance/integration test basically "run" in the new test environment, the new test env:

• generate temporay configuration based on test requirement
• hardcoded docker-compose for basic configuration, new config(for kwild) could be added by change envs
• run required nodes in docker
• should be enough for us to spin up a dev environment. It will panic when boot up kwild rn, so you need to adjust the boot process to make kwild actually run

[sonarcloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
1 Security Hotspot
3 Code Smells

No Coverage information
2.9% Duplication

Catch issues before they fail your Quality Gate with our IDE extension SonarLint

[brennanjl]

Thanks for doing this

[jchappelow]

• It will panic when boot up kwild rn, so you need to adjust the boot process to make kwild actually run

You mentioned this at the meeting, but I don't follow. What adjustments to make and where? Thanks!

Actually, perhaps tomorrow I can sit down with you for 15-20 minutes to get a little intro to the test environments? I haven't had a lot of chance to do so since I started on IDOS and then jumped into kwild just as everything was being refactored. :)

[Yaiba]

• It will panic when boot up kwild rn, so you need to adjust the boot process to make kwild actually run

You mentioned this at the meeting, but I don't follow. What adjustments to make and where? Thanks!

Actually, perhaps tomorrow I can sit down with you for 15-20 minutes to get a little intro to the test environments? I haven't had a lot of chance to do so since I started on IDOS and then jumped into kwild just as everything was being refactored. :)

The current test env stilll runs in Docker, but in a different fashion. But the basic setup has complete, it configures whatever Kwild need to just run gRPC server etc. You should be able to spin up a local instance of everything by run task dev:up, if Kwild actually runs(with all components correctly wired).
So the purpose is with this test environement, we can slowly assemble all the components we need.

Before merge @brennanjl new-transaction structure, kwild will just panic on NoImplementation since the ABCI app is not fully wired with different components, that's the adjustments i mentioned.
After the merge it still panic on NoImplementation but this time it panics on PrivateKey interface. I guess the adjustments becomes to:

• first, avoid load PrivateKey for test setup and Kwild
• second, make Kwild actually run

Actually i think i can make a quick pr to make test setup avoid load PrivateKey, so everyone could just focus on making Kwild run.

Yeah i can walk you through the test environment tomorrow, could use some feedback.