allow parameters for restart effector, including children and the machine for SoftwareProcess.restart;
if this model is sensible we might apply it more widely to effectors, to allow parameters to tune behaviour.
(eg for stop, to allow controlling whether it is the machine or just the process which is stopped,
and on start, to allow forcing reinstall)
fix error where collapsed text would leave out interesting messages included with the propagation, with tests
fix failures introduced by dynamic/parametrized RESTART effector; main items are:
    * factory not calling init (deprecate EntityFactory);
    * do{Start,Stop,Restart} methods not getting invoked (deprecated, replaced by pre- and post- start overrides)
propagate entitlements as tasks are submitted, to fix failing AcmeEntitlementManagerTest
add missing @EffectorParam for policy test; also tweak the test so build completes a bit faster
Fix GeoscalingWebClientTest

- Adds comment to GeoscalingWebClient about trust store.
- Was failing due to certificate not in trust store. For tests,
  run with trustAll
- Also convert from groovy to java
Fix GeoscalingIntegrationTest

- it was not instantiating StubHostGeoLookup
Fix SshMachineLocationIntegrationTest

- It needs the brooklyn.properties contents for named location
  “localhost-passphrase”, so can’t just use `newManagedInstanceForTests`
Fix QpidIntegrationTest

- use correct management URL (otherwise get back 404)
Fix NnginxClusterIntegrationTest

- if use initialSize=0, then serviceUp behaves differently when
  cluster is empty. So don’t do that.
Fix MavenArtifactTest

- URLClassLoader does not follow redirects, so need to do that first
  (for URLs pointing at search.maven.org), before seeing if they
  can be resolved correctly
apply code review for adding parameters to RESTART effector, mainly javadoc and code tidies
Merge and close #270
This closes #260
improve formatting of scheduler's status
add a new main.uri sensor in Attributes, similar idea but wider scope to WebAppService.ROOT_URL
enhance config REST data to provide info so that we get "open REST link" actions, and related cleanup
include parameters in description of effector invocations
call `parentLocation.release(child)` on unmanage, so that (in part) ports obtained for use on localhost are freed up for reuse;
and clean up how the decision to `release` is made with new abstract ProvisioningLocation
add support for extracting flags from $brooklyn:entitySpec declarations and translating them as config