Implement job watching in job launching commands #202
Description
After issuing a command that launches a job on the backend, users typically have to use the jobs:watch command to see the status of their job. That command requires the specific jobId of the job that got launched which makes scripts to automate this more complicated to write.
A better user experience would be to equip each command that launches a job on the backend with the ability to immediately watch the job it just launched. Adding a --watch flag to these commands would do it.
Alternatively, watching jobs could be the default for these commands and a --no-watch or --background flag could tell the command to skip the watching part and return. This is likely what users expect to do but before selecting this approach, we need to consider if watching jobs by default could break existing scripts written by users. Additional output due to watching a job should not confuse scripts into thinking the command has completed. If this is respected then making watching jobs the default should work.