Suggestion: Replace polkadot-launch with Zombienet or parachain-launch

[doutv]

See below for motivation:

• Replace polkadot-launch content with parachain-launch & zombinet polkadot-developers/substrate-docs#1098 (comment)
• Deprecate polkadot-launch in favor of "Zombienet" paritytech/polkadot-launch#189 (comment)
• Replace polkadot-launch content with parachain-launch & zombinet polkadot-developers/substrate-docs#1098 (comment)

[doutv]

I tried to use parachain-launch.

There are some images here: https://hub.docker.com/u/uniquenetwork

Maybe I can use this image? https://hub.docker.com/r/uniquenetwork/quartz-node-public

[Fahrrader]

Reviving this issue with news that we're deploying Zombienet in our CI very soon! It's been possible to use Zombienet natively or with the images you correctly pointed to,

https://hub.docker.com/r/uniquenetwork/quartz-node-public for a Quartz node

and

https://hub.docker.com/r/uniquenetwork/unique-node-public for a Unique node.

But with this PR, test network specs will appear in the root of the repository (and a whole script in tests to launch it), which will hopefully make it easier to get started.

[CertainLach]

We have updated our test infrastructure to use our own parachain launcher: https://github.com/uniquenetwork/baedeker, which has better integration with https://github.com/uniquenetwork/chainql, which we were using for some tasks (I.e chopstics-like parachain fork tests: https://github.com/UniqueNetwork/unique-chain/blob/master/.baedeker/forkless-data.jsonnet).