Add openeo.cloud variant with support for 2.0.0 processes

[JeroenVerstraelen]

No description provided.

[soxofaan]

current openeo.cloud config uses these upstream backends:

openeo-aggregator/conf/aggregator.prod.py

Lines 46 to 50 in 646b1d7

	aggregator_backends={
	"vito": "https://openeo.vito.be/openeo/1.1/",
	"eodc": "https://openeo.eodc.eu/openeo/1.1.0/",
	# Sentinel Hub OpenEO by Sinergise
	"sentinelhub": "https://openeo.sentinel-hub.com/production/",

which use v1 version of processes as far as I know.

We should add a variant that supports v2 processes (e.g. like https://openeo.vito.be/openeo/1.2/)

[soxofaan]

Paths to investigate:

• implement multi-version support in aggregator itself? Would require "adding a dimension" to the config system in some way, same for the metadata caching. Overall possibly quite a lot of places that have to be adapted
• just deploy a new instance with other configs. Is probably less work, but adds operational overhead: more systems to monitor, less efficient resource usage, more configs to manage

[soxofaan]

relevant openeo-api/openeo-processes discussion:

• Federation extension: how to ensure consistent process version across backends? openeo-api#548

[soxofaan]

part of this puzzle:

• Add openEO processes version #517 openeo-api#549

[ValentinaHutter]

current openeo.cloud config uses these upstream backends:

openeo-aggregator/conf/aggregator.prod.py

Lines 46 to 50 in 646b1d7

	aggregator_backends={
	"vito": "https://openeo.vito.be/openeo/1.1/",
	"eodc": "https://openeo.eodc.eu/openeo/1.1.0/",
	# Sentinel Hub OpenEO by Sinergise
	"sentinelhub": "https://openeo.sentinel-hub.com/production/",

which use v1 version of processes as far as I know.

We should add a variant that supports v2 processes (e.g. like https://openeo.vito.be/openeo/1.2/)

We now updated the EODC openEO api, so 1.2.0 is available as well: https://openeo.eodc.eu/.well-known/openeo/