support parsing of job options from UDP definition

[jdries]

Support functionality described here:
Open-EO/openeo-api#471

The goal is to allow UDP's to advertise job options, avoiding failures due to for instance not providing udf dependencies or sufficient python-memory.

[soxofaan]

PR #367 is ready I think. I'll give it a final look tomorrow and merge

[soxofaan]

Open-EO/openeo-api#471 was just merged too (after some more review iterations)

[soxofaan]

merged #367 now

[soxofaan]

before closing (and as proof that it works), when feature is available on a public deployment (e.g. CDSE staging)

• work out example in context of APEx benchmarks

[soxofaan]

Usage example in APEX:

https://github.com/ESA-APEx/apex_algorithms/blob/11c27fb1a90cfc8f2eb285b881d1db8a96c358f4/openeo_udp/examples/max_ndvi/max_ndvi.json#L190-L195

Here I added these default job options to the UDP JSON doc:

  "default_job_options": {
    "logging-threshold": "info"
  },
  "default_synchronous_options": {
    "logging-threshold": "warning"
  }

When this UDP is executed, these default job options will be used (unless explicitly overridden)

[soxofaan]

the official spec/doc of the processing parameters extension also has an example by the way: https://github.com/Open-EO/openeo-api/tree/draft/extensions/processing-parameters