Interop: testing Go helper-funcs / DSL

[protolambda]

• syntax to build the instruction to above contract, and format it as a signed tx ready to submit.
  • contract instruction part → contract call. Also see Interop: build test helper smart contract #14049
    • could use multicall contract, to run multiple instructions in the same tx.
  • fee payment part → can be generous with max-fee, simple to include.
    • May be interesting to make less simple to include later, to stress the sequencer.
      • pre-processing should be prioritized likely, but how big is the load? Does it withstand with or without prioritization implemented?
• interaction to get the tx included in a block → API calls, with some nice client bindings
• interaction to get the tx submitted to regular sequencer
• inspection of post-state:
  • inclusion / receipt data of a tx → DSL to await confirmation / rejection
  • supervisor result → the dependencies we created, query supervisor API to see if e.g. the block becomes cross-safe.