Wait for a capability by the name of the capability given dynamically.

[Niranjan-K]

[Moved from carbon-kernel jira]

Current required capability listener can wait until the given number of capabilities are available, but this number of capabilities are decide at the compile time and there is no way to decide them dynamically at the run time. There are some use cases where the component should only wait for capabilities that decided by a configuration file or some run time configuration. To cater this requirement, following features will be useful.

1. Feature to decide required capabilities in the run time based on an OSGi property and to give the list of required capabilities dynamically.
2. Feature to give a custom error message when a capability is not available as the current error message is only showing what type of capability it is waiting for.
   See mail: Improvements For The OSGi Required Capability Listiner

[Kishanthan]

We also need to specify some capabilities need not to be resolved via StartupOrderResolver and skip (may be using a a service property). This is needed in the UUF case where for each UUF app, there is a microservice deployed and it does not need to be handled with StartupOrderResolver