Raising a job's timeout no longer requires changing its compute

Previously, PATCH /v1/jobs/{id} with only a larger timeoutSeconds returned 400 with "Invalid integer" when the new timeout exceeded the job's compute.durationSeconds. Now the update extends compute.durationSeconds to the timeout plus 60 seconds of start time, up to 3,600, as a create does. A timeout that already fits leaves it as it is. Refusals of timeoutSeconds and compute.durationSeconds now name the field and the allowed range.