Support Prefer: return header for /results endpoint

[fmigneault]

Description

Allow Prefer to request an alternative GET /jobs/{jobId}/results response representation.

When Prefer: return=minimal|representation, response=raw|document and/or output-specific transmissionMode: value|reference are used during Job execution request, the results are adjusted accordingly for the response.

Note

since response and outputs cannot be submitted again in the GET results request, requesting a Prefer should rely only on OGC API - Processes v2.0 return strategies. However, a response=raw|document query parameter might be considered.

Requirements

• Using a subsequent request to /results using Prefer should allow "ignoring" the original results representation saved in the Job.
• Using a ?response=raw|document query parameter for /results would allow doing the similar resolution to the response body parameter during job submission.
• Support outputs query parameter for /results #733
• Add test to validate combinations, for single output and multi-output cases
• Combining with Accept should allow appropriate resolution
  • as response=document if multi-output
  • Support ZIP output #726
  • update metadata doc links #257
• Resolution of the various Prefer/response/Accept combinations must be equivalent to the resolution order of job submission (see job execution results #713)

References

• relates to Support Job execution Prefer: return header #414
• relates to job execution results #713