Adress last OSGi merge comments

@ahgittin maybe we misinterpreted the TODOs?

Is "test registering entity from the bundle using new registered name" the `testLaunchApplicationWithCatalogReferencingOtherCatalogYaml`? i.e. register a catalog item that uses an entity in the bundle, and then register another catalog item that references the first catalog item.

Is "test registering entity from the bundle using type of item and the registered name (check endless loop)"  covered by:
* `testLaunchApplicationWithTypeUsingJavaColonPrefixInYaml`: the serviceType uses the "java:" prefix, but other than that has the same name.
* `testLaunchApplicationLoopCatalogIdInYamlFails`: catalog item's serviceType references itself (i.e. circular reference) fails with nice message, rather than `StackOverflowException`.
* `testLaunchApplicationLoopWithJavaTypeNameInYamlFails`: the serviceType is the same as the java class, but matches the catalog name - fails with nice message, rather than `StackOverflowException`.

For the last one, this is the controversial one discussed on dev@brooklyn. @richardcloudsoft and @neykov both think better to be explicit, to apply rules consistently, and to fail with nice message in this case. I was on the fence for keeping the yaml as simple as possible, but on balance agree that consistent rules is better than making this a special case.

Did you mean some other tests with these TODOs?