Use classloader with access to all capability interfaces in CapabilityInstance proxy.
Implement isSupporting in BindingManagement supporting only core resource.

Avoids following message when loading core bundle:
No way of establishing bind with Capability org.mqnaas.core.impl.BindingManagement. No isSupporting(...) implementation found.
Add some logging messages in BindingManagement (using System.out)
Rename methods in IBindingManagement and IInternalResourceManagementListener.
Extensions may use IResourceManagementListener interface to react to resources going in and out of the system.

In order to do that, an application has to:
1) resolve IObservationService (may be injected if marked with @DependingOn)
2) register a service with a service filter matching the execution of service IResourceManagementListener#resourceAdded(IResource) or
IResourceManagementListener#resourceRemoved(IResource)
See MyTestsApplication.java for details.

This patch allows that by following means:
BindingManagement now offers services in IResourceManagementListener and registers them to be executed.
Services in IResourceManagementListener are executed AFTER BindingManagement has processed the real event, which means that:

When IResourceManagementListener#resourceAdded(IResource) is executed:
- Added resource is already in its capability internal model.
- Added resource is already bound to all existing capabilities that should be bound to it.
- Bound capabilities that can be resolved are already resolved.

When IResourceManagementListener#resourceRemoved(IResource) is executed:
- Resource is already removed in its capability internal state.
- Capabilities that were bound to removed resource have been already removed.
- Any Capability or Application having removed capabilities as dependencies has been unresolved.