Use weave network to run internetless CATs suite in EKCP

[mudler]

We need also to make the same change at the ekcp backend in Catapult so we can test also in CI. Note we can post also a kindconfig (is not documented anywhere.. my bad) https://github.com/mudler/ekcp/blob/b585bb2a22393f9b870651da06428917fdd6cf7c/api.go#L36 , so it should work somehow like this:

curl -d "name=test&kindconfig=$(base64 kindconfig.yaml)" -X POST http://127.0.0.1:8030/new

Originally posted by @mudler in https://github.com/SUSE/catapult/pull/156/files

[viccuad]

Tangential to this issue yet relevant because it may share implementation:

For creating and destroy terraform clusters on the cap-release pipeline (caasp4os, public clouds), I've come to the conclusion that the minimum unit of work for clusters should be a slimmed down buildfolder, containing kubeconfig, terraform folder, and in kind case, kindconfig.

This buildfolder would be added to the pool, and there would be a dirty pool where the clusters either get cleaned or destroyed, making use of the files in the buildfolder.