Define Integration of OGC API Coverages and OGC API Maps into eoAPI

[j08lue]

We are planning to extend eoAPI with OGC API Coverages and OGC API Maps services.

We need to define how that integration will look like, so we can design and document the target architecture.

Acceptance criteria

• [x] Recorded details of integration
• [ ] Documented the target architecture

[j08lue]

Based on my understanding, the internal architecture of the building block will look somewhat like this:

Each library, eoAPI and Stacture+Terravis, is included in its own right, with each its docs and tests.

In default configuration, the two libraries provide a complementary set of endpoints, although they can also be configured to run in non-BB mode with a more complete set of features.

Stacture+Terravis connects to eoAPI's STAC API.

@constantinius, does this match your understanding at this point?