Starship integration

[Anmol1696]

Overview

In this PR we add starship integration and tests.

Implementation

• Add tests/starship dir
• Move tests/e2e/testdata to tests/testdata, so that the same contracts and be used for e2e tests as well as starship tests
• Run starship tests in the CI
• Test case:
  • 2 way mesh (making both chains and consumer and producers)
  • Move assets around
  • Qeury contracts/states
• Created tests/starship/setup pkg to initialize chains with the mesh contracts and perform e2e handshakes

CI

CI has been tested here: https://github.com/osmosis-labs/mesh-security-sdk/actions/workflows/starship-e2e-tests.yml

Why

With starship we are able to test against

• actual chain binaries (currently still running against demo app, but when ready can be run against actual chain binaries)
• actual relayers (using the hermes relayer, with config to pull)
• ability to create a full mesh (for tests and also internal devnets)

Starship also gives a nice playground and a good start to be able to create an integrated qa environment.

Since Starship acts like a complete blackbox testing framework (we only interact via RPC endpoints), work needed to adapt tests/e2e tests where all functions and steps to initialize new chains with mesh-contracts gets codified and tested. We make little to no assumptions about the infra, so can easily create a util to initialize contracts.

Starship integration will also give chains that want to adopt mesh-security a way to quickly test out compatibility via and e2e testing setup.

Future work

• Make tests/starship/setup pkg integrated with tests/e2e package
• Add more scenarios with multiple chains, creating an actual mesh
• Cloud k8s integration for running a bigger and longer devnet
• Add more tests scenarios

Limitations

• Contract setup takes long time: around 8 mins (this can be sped up)
• Transient errors: Since there are alot of moving parts, there are still some cases of transient errors (we are working on eleminating them completely, one at a time). System will get more robust with time

[alpe]

Very nice start! Thanks for driving this forward!
I have not looked at the test details. yet but I was wondering how this PR relates to #55 and what the bigger picture is?
With starship tests in tests/ folder, I would expect them to run in CI. Is this what you want to do?

[Anmol1696]

@alpe sorry you had to review this, but this is still a draft PR and is not fully ready to be merged.
I will take your points into account when I open this PR up properly.

[Anmol1696]

As for what the bigger picture is with Starship, we can make an issue or a design doc of sorts needed.

But yes we will run these tests in the CI as well, as well as for setup for anyone who wants to use Starship, for let's say frontend, backend or even contract development. I think we have to figure out where best to place the starship dir, but it is self contained and can be placed anywhere.

[Anmol1696]

No sure if we want to run this on every PR, takes around 15mins to run the CI

[JakeHartnell]

Thank you for this work, the demo we showed at Osmocon would not be possible without it. 🙏

[alpe]

This has been pending for some time due to my other responsibilities. Sorry for this!
I think it is good to get this rolling and see how this adds value. I have not looked deeper into the code as it is not touching the MS code. But I assume @JakeHartnell did, so let's merge and let CI do some work. ;-)