Provide binary for test service

[bkchr]

The test service is currently only used by integration tests. There is a builder pattern for building a node with the wanted features. Most of these integration tests should be rewritten with Zombienet. This will require a binary that can be started. This binary should basically expose the builder pattern via cli.

The builder currently also uses in memory addresses for libp2p. This will not work when the nodes are their own processes. So, this needs to be changed as well to also support normal libp2p multi addresses.

Cc @pepoviola

[skunert]

@bkchr That means we also need the polkadot test service as new binary right? To start the relay chain nodes for these integration tests.

[bkchr]

Probably yes, but maybe we can also just use rococo as runtime. Needs to be checked.

[skunert]

@pepoviola I have draft open for the testing binary #1158.

Mostly the node remains the same from what we have in our current integration tests. From what I understand you will migrate the first test for us right?

Mostly I exposed networking configuration like node-key, so we can do address calculation in zombienet.
Supported options:

--parachain-id
--relay-chain-bootnodes
--alice, bob, ...
--reserved-nodes
--reserved-only
--node-key
--bootnodes

// following arguments are used to build specific scenarios for the tests
--use-null-consensus
--disabled-block-announcements

Will that be enough for zombienet? Let met know here if you need more options on it.

As for the relay chain nodes, will look into using rococo.