Change webservice-cli so it goes through the jobs-api endpoint instead of talking
to Kubernetes directly.
toolforge webservice start becomes an alias for toolforge jobs run --webservice (using the endpoint though, not the cli),
similar to toolforge jobs run --publish ... webservice.
The job is a continuous job named webservice, with the webservice defaults from image-config.
toolforge jobs dump should then give back an actual continuous job with those
webservice defaults set.
That lets us remove most of the logic out of webservice-cli. Status, restart, stop
and logs all go through jobs-api too.
webservice shell stays as it is, unless we add support for shelling into containers in jobs-api too.