Add ProvideConfigurator Annotation for Convinience

[bjhargrave]

Original bug ID: BZ#3053
From: @juergen-albert
Reported version: R7

[bjhargrave]

Comment author: @juergen-albert

We provide a convenient annotation to require a specific configuration. Thus it would make sense to provide an annotation for a provider of a configuration as well. The effort should be minimal, because it should simply be a copy of the RequireConfigurator Annotation and replacing the @ Requirement with @ Capability (plus JavaDoc change).

[bjhargrave]

Comment author: @bjhargrave

We had discussed Capability annotations in general some time back. Mostly is was not deemed terribly useful since there are often only a few capability providers when there are generally many capability requirers.

So, in the example here, there are relatively few bundles that will provide the configurator implementation capability. So there was not sufficient need to define a standard annotation for the few configurator implementation authors in the world. They can simply put the capability in their manifest or define their own capability annotation to get Bnd to put the capability in the manifest.

[bjhargrave]

Comment author: @juergen-albert

Sorry, my Mistake. I was under the impression, that this annotation could be used to require a specific configuration and not the configurator itself to apply for my bundle.