AppOrSpec not relevant any more, remove.

The code uses only the spec part.
Rename getCatalogIdOrJavaType to getBrooklynType.

The type now can be one of:
  * catalog id
  * java class name
  * URL to yaml file
Split spec creation in separate steps to allow re-use.
Load URL referenced YAMLs.

Allow URL references to YAML files in addition to catalog IDs and java types.
Currently limited to services (PlatformComponentTemplate level).

In the case of more than one service in the referenced plan just use the wrapped app as a child.
The template referencing the yaml will override the name, IDs of the child. Locations, policies,
effectors, ect. will be appended to the child's config. Do the same for catalog item references.
Resolve catalog items and yaml URLs from child entities as well.
Remove unnecessary name in YAML.
Add tests

  * Catalog item does not leak bundles to child catalog items
  * Catalog item DOES leak bundles to URL referenced YAMLs
Log a warning

in case the protocol of a url referenced YAML is not white listed
fix intermittent issue with apache rat

those files are not always considered binary, but they are not directly used by code
This closes #71