Hide or mark proprietary processes

[m-mohr]

Originates from https://github.com/openEOPlatform/architecture-docs/issues/21:

Some processes are available just at one back-end, but are pretty specific to the back-end or some data or so.
We think these should be hidden or marked explicitly as experimental processes or as being unavailable at some back-ends.

For example, some of these processes that are available at VITO:

• discard_result - Use case unclear
• get_geometries – No file storage supported right now
• load_disk_data – No file storage supported right now, once available replace with load_uploaded_file instead?!
• sleep – Use case unclear

[soxofaan]

I think this is partial duplicate of (or at least related to)

• Federation of (predefined) processes #4

Initially the aggregator exposed only the intersection of processes across back-ends, but then for pragmatic reasons we decided to work with the union.

[m-mohr]

I think the union is still fine, but unrelatedly we may need to either have a black-list or handle some processes in a special way, I think. Long-term we may even switch to a white-list so that only "approved" (tested and aligned) processes are listed...

This issue was meant to focus to handling the specific processes short-term, which is probably somewhat independent of the long-term solution.

[jdries]

seems low priority but we can perhaps do something easy in the documentation