We have https://phabricator.wikimedia.org/T423408 which introduced support for --publish,
and is the actual way to handle exposing the job to the internet like the webservice.

Support for this --webservice option is needed because --publish is lower level and requires the user to specify things like port, command, continuous job, etc.
--webservice should help abstract all of that away and look more like what users are familiar with in webservice-cli.

this involves:

• adding the --webservice option to toolforge jobs run on jobs-cli.
• specifying the --webservice option should call a dedicated webservice endpoint on the jobs-api, which handles creating the continuous job with --publish and all the webservice defaults