allow restarting job during patch

Currently we only react on the Job object differing between the user provided config and the config from the runtime.

There are cases where it is useful to restart a job, such as in components-api, for example when the backing image has changed, but the tag is still the same.

We support /restart already, but this would require exposing logic and then having the client perform the steps to check if a change is needed, then apply it, or just restart; we can easily hide all of that in the API.

Depends-On: !220 (merged)
Bug: T403321