Chopsticks + CI/CD

[samelamin]

In addition to being the authors of Chopsticks, Acala also has a good e2e tests repo that is generic enough that all chains could use assuming they added the correct configs.

It would be good if we had a chopsticks test running on CI that validates that the new runtimes work as expected with the existing chain state

I am planning on building a GitHub workflow that

1. Builds all the runtimes
2. Tests an XCM transfer between Kusama and assethub

Let me know if the above approach is unreasonable or if I should change it in any way

We can add more tests as we go along but just having that as a start would go a long way and hopefully help builders to ensure they test their changes against their live state and avoid future bricking of the chains

I think using the e2e test repo is good if we want to ensure consistency across the board but if we want to only use chopsticks we can but the tests will be slightly harder to build

Is there a potential issue of using an external dependency like the e2e tests repo in CI? because we would be just as dependent on chopsticks unless the fellows fork it?

[bkchr]

Somewhat a duplicate of: #171