OSGi class loading fixes

  * Changes the way bundles on the classpath are exported to felix - from list of exported packages in system.packages.extra to building extension bundles for each bundle on the classpath. This avoids the case where the same class would be loaded once from the classpath and once from a bundle referenced by a catalog item. When the catalog item tries to install the bundle we see that there is already an existing version installed and use it instead.
  * AggregateClassLoader doesn't relay to parent, using only the explicitly registered classloaders.
  * Force maven-bundle-plugin to include \*.impl.\* and \*.internal.\* packages in the export-package list (referenced between brooklyn bundles)

***NOTE***
Installing all the bundles in brooklyn-dist on my PC takes 3 seconds (once on startup). The slowdown is in Felix itself. Since we will be moving to OSGi based app we will need to load the bundles anyway so I don't see a way out of this.
Looking at the code I didn't find a case where spec.getImplementation() != enttiy.getClass() - the entity is always instantiated from getImplementation() if available. 
Event if that's the case and the classes (and possibly the classloaders) differ why would we want to use the classloader of a class which didn't instantiate the entity instance?
Looking at this code again I think that it should be improved but in another direction - adding the classloaders of all extended classes and interfaces recursively, not only of the explicitly specified interfaces. WDYT?