Bug 1154678 - [EAP6] - Newly created datasource is not enabled even when you have set Enabled=true -- user should be at least warned

When the datasource was created, the 'enabled' attribute was supplied to the EAP6 management interface.
But setting the attribute to true does not enable the datasource. An extra server reload is needed.
To enable a datasource without a server reload, the 'enable' operation needs to be called.

So now the DatasourcesComponent class:
-> no longer supplies the 'enabled' attribute to the CreateResourceDelegate
-> reads the state of the datasource after creation
-> invokes the 'enable' or 'disable' operation (as needed) after creation
Bug 1154678 - [EAP6] - Newly created datasource is not enabled even when you have set Enabled=true -- user should be at least warned

Fix error in connection properties management code: do not clutter the created datasource Address

(regression detected in Jenkins)
[BZ 1070262] Fix agent packaging to set the picketbox version for ant-run.xml script via maven pom; remove unused dom4j and commons-httpclient libraries.
[1139735, 1157480] More upgrade use cases that didn't work.
[1139735] An upgrade with a number of storage nodes > than our replication
factor (>= 4) could fail because our check for the storage cluster
version can fail if the auth info or version info are not replicated
to the currently running SNs.  To avoid this, for ugrades we now push
all storage cluster interaction to the post-upgrade step (i.e.
rhqctl --storage-schema).  This includes the schema creation for a new,
remote storage cluster.

[1157480] An upgrade of standalone storage node can fail because those
installs may not have set proper DB props in rhq-server.properties.  It
wasn't required in the past but it is now.  In the code we now make sure
the properties are copied forward on upgrade. But there is also doco needed
here because prior to upgrade from an earlier version, using standalone
SNs, the old rhq-server.properties files will need to be updated.

Also, update the --list-versions report to better reflect that it may need
all SNs to be running to perform the storage schema version check.
Bug 1158516 - Number of platforms retrieved using REST can't be modified
using ps param and is always limited to 100

set @DefaultValue to 0 for page parameter. Without that paging was disabled
unless page query parameter was specified.
BZ 1158228 - to support install on Windows, allow for agent to be told to reload its agent config xml via marker file
BZ 1158948 - make sure agent can start/stop via rhqctl on solaris 10
[1157480] resolve a test issue by better supporting a missing
rhq-server.properties file if the --no-version-stamp option is specified.
[1159003] Alert notification sending fails due to database deadlock error
Remove the umbrella Tx surrounding sending of alert notifications.  It used
to be that all notifications would be sent in one REQUIRES_NEW SLSB call. It
was necessary to do this because the notifications were themselves sent
within a larger, very heavy, umbrella Tx that involved the alert generation
itself (among other things). Prior work restructured that logic and
moved notification sending to a more logical place, executing after
alert generation, cache update and recovery logic handling.  But the prior
work left the notification sending under a single transaction.  This
isn't really necessary or desirable. Each notification should be processed
individually, not holding any resources past its execution, and
persisting each notification log in its own Tx.  Although not proven,
the deadlock situation was likely caused when an alert definition defined
multiple notifications, and one held resources required by another.

Also, rename some local SLSB methods with "Tx" suffixes to better reflect
their behavior.
[BZ 1158892] Remove AllEndpointStates property of FailureDetector service from the plugin descriptor. This will prevent a high curn of configuration changes for the service due to the ever changing nature of the property. The property is not needed at this point by any functionality in the Cassandra or Storage Node plugins.
Bug 1139189 - If a server is in 'MAINTENANCE' mode, should be indicated to
user on login

Now we display sticky warning in case mainenance mode is detected after
login. This does not add a check for server mode to every request, just the
first request after login - this is when we build CoreGui
[BZ 1003211] Adds automatic recovery information to the alerts if there's a recovery alert fired.

[BZ 1003211] Add hovering support, and also add naming filter to the reports & REST interface