fix saveIptablesRules
addressed comments for saveIpTablesRules
Adds basic instructions for setting up IDEA Intelli-J, and also some debugging tips
Adds resolution to IntelliJ compilation issue, with reply from JetBrains
Javadoc
Remove apache header from install config files

- These are files "without any degree of creativity" from the
  perspective of the Brooklyn/Apache contribution.
  These files originate from the install artefacts of things to be
  installed, and are often templated to make it easier to inject
  port numbers etc.
Remove apache headers from web-docs

- These files are only used to generate the brooklyn web-site.
  Including the apache header results in a lot of noise in the 
  code/configuration snippets within those web-pages.
Remove apache header from archetype files

- The maven archetype are files "without any degree of creativity". 
  They are intended purely as a template to generate a new project 
  for a user, where upon the user can write their code within this 
  new project.
Mark `HasNetworkAddresses` as @Beta
For “install config files”, add to NOTICE

- for config files we’ve copied from other projects, add a reference
  to each in NOTICE
BROOKLYN-71: DelegateSecurityProvider listens to property changes

Reloads the provider when notified and forces existing sessions to
reauthenticate.
fix intermittent deleting-dir test failure by waiting for server shutdown before deleting dir
better logging and tighter assertions to debug jenkins-failing ServiceReplacerTest, and extracted unit test isolating the problem
set service up before expected running in TestEntity to correct test failures
useful logging if setting expected RUNNING when service is not set up
set transitioning fields on cluster when resizing to or from 0, and better comments on failures
add repeat-untils for some brooklyn-GC-related tests (maybe there is a 1ms window between tasks finishing and that fact propagating thus the tasks being cleanable...)
better log for service state logic
back out logic where DynamicCluster tried to be smart about setting transitions starting/stopping when resizing from/to size 0;
now it does not. 0 is not a valid size for a running cluster. makes sense as a default. notes for how to do something different here.
also minor tidies to ServerPool which was sensitive to this behaviour.
Split rest request filter logic up

* Rest API logging much more limited: GET/HEAD logged at trace, others
  and errors at debug.
* Adds brooklyn.rest.filter package.