Slight inconsistencies remain in APIv2 resources

[Jeremy Freudberg]

For example, the object returned in POST/GET/PATCH/DELETE on the /v2/job-templates endpoint is of the form {"job": ...}, and for /v2/jobs it's of the form {"job_execution": ...}.

You can see that those keys are the legacy name of that kind of resource. That's a holdover from APIv1 and it has to do with Sahara's data model, going down to how the conductor module works.

It is possible to refactor a bit, and we should do so, before moving APIv2 from EXPERIMENTAL to CURRENT/SUPPORTED.