Setup structure in the OGC API Record for supporting multiple deployments of the same service (openEO & AP) (AI80)

[JanssenBrm]

The current structure of the OGC API Record allows defining a platform where a UDP or API Process is available and can be executed. However, there may be multiple deployments of the same algorithm. For openEO, this means a UDP might be executed on different backends, while for an OGC Application Package, it could mean the same application is available through multiple OGC API Processes.

The existing structure of the record does not seem to fully support this setup, as each deployment has its own associated cost model. The objective of this ticket is to explore how the record structure can be adjusted to accommodate multiple deployments of the same algorithm, each with potentially different configurations and cost models.

One example is to introduce the structure of a deployment:

 {
    "platform": "Hosting Platform A",
    "endpoint": "<openEO backend / OGC API Process>",
    "costModel": {
      "type": "<type>",
     "unit": "<unit>",
      "pricing": "<price>"
    },
    "version": "<version>"
  }

[jdries]

the proposal seems reasonable already. So at top level we would add something like the suggestion below?

'platforms': {
platformA: {...},
platformB: {...}
}