[BZ 1139780] UndoTasks are done in reverse order, so add stop command after the delete command to the undoTask list
Bug 1079303 - Excessive database size when using bundles causing UI to fail

Do not load histories when showing the deployments view.
Fetch histories aync when unfolding a resource deployment.

Added index on resource deployment id in audit table
->Fast fetch histories aync when unfolding a resource deployment in the UI
Dropped foreign key on resource deployment id in audit table
->This is to prepare the async deletion of orphan audit messages when deleting a bundle deployment (or a bundle version, or even the bundle itself)
->Documented in db-upgrade.xml and content-schema.xml why we are breaking the rule (dropping an FK)

Added GUI messages when deleting version/destination/deployment/bundle so that the user gets correctly informed of what is going on

No longer cascade remove audit message when deleting resource deployments
Purge orphaned audit messages in DataPurgeJob
No direct purge of audit messages during async resource deletion job

Also, increased the default batch size property, as testing showed 1.5x higher performance (tested on 1 million and on 5 million rows).
A community user with a large RHQ deployment reported better results with higher batch size as well.

getBundleResourceDeploymentHistories returns a copy of resourceDeployment.getBundleResourceDeploymentHistories():
1. It's safer (no direct entity collection manipulation)
2. GWT Serializer does not accept Hibernate's persistent bags
[1138328] globally uncaught exception on storage metrics admin page
Although I was still unable to reproduce this bug I did find a couple of
places where we needed to shore things up, that perhaps contributed.
- fix getResourceIdFromStorageNode utility to throw the correct exceptions,
  this solves issues where caller catch definitions were not catching.
- when uninventorying a Storage Node Resource we did not pro-actively unlink
  it from the StorageNode entity.  We did the unlink in the async work but that
  that left the bad resource linked until async job ran or until
  it was re-linked to a newly imported SN resource.  Now unlinked up front
  (which is unfortunate as it adds another db query per batch).
Bug 1062789 - Set quoting to enabled for newly created script server resources

Changed "quotingEnabled" attribute default value
Made ScriptDiscoveryComponent implement ResourceUpgradeFacet
Tracking upgraded resources with an hidden plugin config property ("quotingEnabledNeedsUpgrade")
Logging message when a Script Server component is started and "quotingEnabled" property is missing
Updated the "getConfiguredEscapeCharacter" method of the Script Server component class
[1128151] Error while upgrading from JON 3.1.2 to 3.3: [rhq.autoinstall.server.admin.password] must exist and be set to a valid string value
Ensure that the property gets a string value assigned during upgrade so that
the properties file passes validation. The dummy value is "ignored-on-upgrade",
the rhqadmin user will already exist in an upgraded server's DB.
[1078500] SEVERE error in Server.log file: JSF1051
This is generated due to, I think, EAP Bug 1141373.  The error does not
seem to negatively affect rhq/jon, so at this point I'm just filtering
out the message from the server log.
[1035420] OOB content labels get cut off
Analogous fixes for the measurement portlets
BZ 1141175 - make sure installer works even if the management bind address is set to 0.0.0.0
Related to work for 1138328. Wrap the new non-async uninv work for
storage node unlinking in a new Tx, like the other work done in that
method.  This may prevent an Oracle locking issue seen in test code cleanup
where we call both the sync and async uninventory in quick succession,
under potentially the same umbrella Tx.

(cherry picked from commit 1fc62b1044225f5cc48033de3783d19b1b047c9e)
Signed-off-by: Jay Shaughnessy <jshaughn@redhat.com>