Support testing Kitsune2 without Holochain

[ThetaSinner]

Possibly this can be done by adding a runner/bindings that can be used to call Kitsune2.

That would assume that Kitsune2 has something like an in-memory host implementation though.

There is a difference between this and what we've done for testing Holochain. Wind Tunnel currently assumes that either Holochain or TryCP are already running. That needs to change for Holochain and it probably makes sense to have the scenario start Kitsune2 itself

We'd be deferring:

• Testing new agents joining an existing network with data
• Agents who have been creating data offline, or otherwise just offline, while other peers on a network are producing data

Dependency:

• Production bootstrap2 service is available, or a perf test instance if it's not going onto cloudflare

AC:

• A thin file-chunking app built on top of Kitsune2 can be operated by Wind Tunnel #137
• Tests the case of multiple agents starting at the same time in a clean network
• Can measure the time taken for files to be synced between peers
• The test can be run for a period of time and files still sync

[ThetaSinner]

We need to decide whether we want to implement a persistent version of the test in-memory host for Kitsune2. If not, then we should focus on building towards having enough functionality in Kitsune2 to be able to complete this task.

If we're able to demonstrate something like a thin file-chunking app built on top of Kitsune2 with either persistent or in-memory op storage is functional then we are probably close to being able to integrate Kitsune2 back into Holochain.

[ThetaSinner]

Waiting for refinement/design on the file share app before refining again