Kubetools

- Allow to run upgrades and tests on any container using a containerContext. Especially allows containers that use a released image rather than a Dockerfile

- Ensure docker compose configs are always generated relative to the kubetools config file
- Fix use of `--debug` when using `ktd`

- Fix issue when creating new deployments alongside existing ones
- Fix `kubetools restart`

- Fix cleanup failure in removing namespaces which contain replica sets

Breaking note: this change passes all non Kubetools specific container config through to the generated K8s container spec. Any invalid/unused data would have previously been ignored will now be passed to K8s and throw an error.

- Pass any non-Kubetools specific container config through to K8s container spec
- Implicitly create target namespace if it does not exist
- The `--cleanup` flag will now remove the target namespace if empty
- Add `-f` / `--force` argument to `kubetools restart`
- Add `-e KEY=VALUE` flag to inject environment variables when using `kubetools deploy`
- Replace `yaml.load` with `yaml.safe_load` to avoid CLI warning
- Fix issues with listing objects in `kubetools restart`
- Fix the test condition for upgrades

- Fix `-f` / `--file` handling NoneType attribute error (introduced in v11.1)