Support /results/{id}/{N} and /outputs/{id}/{N} endpoints

[fmigneault]

Description

Given an output that happens to be an "array" (or rather, a multi-value result of any data format or media-type representation), adding an index sub-path could allow retrieving that specific reference. This could be useful for extracting a specific result used for chaining to another (or multiple) process(es).

In other words:

/jobs/{jobId}/results

{
  "result": [1, 2, 3]
  "urls": ["https://.../1", "https://.../2"]
}

/jobs/{jobId}/results/result

[1, 2, 3]

/jobs/{jobId}/results/result/1

2

/jobs/{jobId}/results/urls

["https://.../1", "https://.../2"]

/jobs/{jobId}/results/result/0

https://.../1

To Do

• implement the endpoint by index
• raise an "out-of-range" error if the index is invalid or does not apply (not an array value)
• handle content-negotiation as applicable for that indexed-value

References

• relates to Add minOccurs and maxOccurs to output description opengeospatial/ogcapi-processes#414
• depends on Support /results/{id} and /outputs/{id} routes #18 (prefix endpoints by ID)