Refactor existing e2e tests to take traces as inputs

[p-offtermatt]

We want to get rid of the hardcoded test cases for e2e tests in our Go code, but instead take test cases from files, which will make our tests more reusable.

Potential formats for traces

• The format used by difftests https://github.com/cosmos/interchain-security/blob/7bc407ce5647fe66f22022705b0849ce69d31e8f/tests/difference/core/driver/traces.json
• The Informal Trace Format https://apalache.informal.systems/docs/adr/015adr-trace.html
• Marshalling/Unmarshalling the JSONs directly

Closing Criterion
The e2e tests read the action/state sequences from a file in some standard format.

[p-offtermatt]

For now, I will implement a parser for the ITF format.
Some aspects need special care:

• The ITF format has no standard way to specify that only part of the state is relevant - it usually expects the full state after each action. This information could be added in the meta field for each step, or we can implicitly only list the state we care about

[p-offtermatt]

Going for the ITF parser first seemed unhelpful, since it seemed hard to get correct inputs to test the implementation on, so for now, I decided on implementing a simple JSON writer/parser that unmarshals/marshals the classes that already exist in the code.

Other writers can follow later as separate issues.

[p-offtermatt]

Issue was not closed by PR merge for some reason, so closing manually.