Jobs should be its own standard, co-branded with Common

Part 1 should be split into two documents

• OGC API - Jobs - Part 1 / OGC API - Common - Part 6
  • Every GET operation on /jobs and its sub-resources
  • DELETE on /jobs/{jobId}
• OGC API - Processes - Part 1
  • The rest of the current document, depends on Jobs Part 1.

Rationale:

• Other OGC API standards that support async requests are also using the Jobs endpoints without the Processes overhead. In Features, OGC API - Features - Part 10: Queries and and OGC API - Features 11: Atomic and batch transactions are currently using them, but do not have a good dependency to reference. If that would exist, OGC API - Features - Part 4 / OGC API - Common - Part 5: Create, Replace, Update and Delete would reference the Jobs standard, too.
• Because the Jobs resources can be reused in other contexts outside of Processes, it should be co-branded with Common.