Capabilities: enable/disable API based on capabilities (OAS + OASO)

Make the list of enabled/disable controllers in OAS reflect enabled/disabled capabilities.

Acceptance criteria:

• OAS allows to specify a list of enabled/disabled APIs (e.g. watches, caches, ...)
• OASO watches capabilities and generates the right configuration for OAS with enabled/disabled list of APIs
• Documentation is properly updated

QE:

• enabled/disable capabilities and validate a given API (DC, Builds, ...) is/is not managed by a cluster:
• checking the OAS logs do/do not log entries about affected API(s)
• DC/Builds objects are created/fail to be created