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.
this will totally ignore the extension, right?  do we need to try to load via the bundle being extended?  or maybe, if extension bundles are installed, attempt a second pass which tries again to load via the non-bundle extensions?

(my understanding is that, if i had  `bundle-A`  and  `extension-A1-for-bundle-A`,  i'd have to install `bundle-A` first into the OSGi container, but an attempt to `loadClass("ClassInExtensionA1")` on `bundle-A` would fail until i've installed `extension-A1` -- but the code here doesn't attempt to reload with `bundle-A` after installing `extension-A1`.  please correct me if i'm wrong!)