[1160682] Upgrade from JON3.1.2 to JON 3.3 CR01 with run-data-migrator option shows AuthenticationExceptio
This happened because the storage cluster schema is not yet created.  It
won't exist until 'rhqctl upgrade --storage-schema' is executed, after all
RHQ Servers have been upgraded and standalone SNs have been installed.

Removed the rhqctl upgrade '--run-data-migrator' option.  This option really
should never have existed, as for anything other than a basic topology it
would have failed, even in the past.  The data migration must be performed
after the full upgrade has completed, including the --storage-schema option,
using the command line tool: 'bin/rhq-data-migration.sh|bat <options>'

Also updated the upgrade/list-versions report to better instruct users
performing pre-storage-cluster upgrades (e.g. jon 3.1.2)
[1160669] Failed upgrade of standalone storage node is not correctly rolled back
This was true of any storage node upgrade failure, not just the new
db properties issue reported.  But the new properties is the most likely
new reason for a failure.  Changes to fail the overall upgrade on any
non-OK status returned from the storage upgrade.  This shouldbe safer, and
prevents the server from trying to upgrade if the storage upgrade has an
issue.

Also:
- added a specific error exit code for version stamp failure
- enhanced some undo task log messages
BZ 1160851 - add the ability to wait for N seconds while testing for the server to come up. Default is 60s, but there is now a backdoor sysprop you can set if you want it to be longer or shorter.
Bug 1133590 - Unable to login in to 'Red Hat Access' in IE

After investigation with chindley, the issue is fixed on JON side, just by
adding IE=10; to X-UA-Compatible meta. IE9 won't work anyway, because it
does not support CORS
[1092707] If re-install is attempted using a different storage node host name, install fails
During install, contact the storage cluster using the DB defined storage
nodes if they are already managed (at least one is linked to a resource),
otherwise defer to the rhq.storage.nodes property value and redefine the
persisted storage nodes with the [potentially] updated addresses.
[BZ 1161806] Fix the slice being wrongly computed after a DST transition. If the duration of the time slice is more than one hour, account for the timezone offset and adjust the time slice start time. This will address the issue where the query for time slice data was not returning data due to the a skewed start time.
Bug 1144035 - DynaGroup Children table is not visible where the 'display
resolution' is 1366x768

Set min member size to dynagroup child table
Bug 1036101 - BRANDING: JON alert email report says "This message was
delivered to you by RHQ."

EmailManagerBean now looks up productName and puts it into alert-email body
[BZ 1162182] Add support for btrfs, zfs and f2fs
[BZ 1127481] Add mount options as traits to the filesystem monitoring
[BZ 1161806] Switch the entire server metrics code to use an UTC timezone in all the code. This will avoid any DST issues since there is no DST in UTC timezone. Also, this will avoid any problems due to having an HA environment where the servers are distributed in different timezones.
[BZ 1161806] Shift the timeslice to a correct UTC timeslice during the index migration. This will gurantee that during metrics index updates the new indexes have slices based on UTC timezone.
[BZ 1161806] Fix broken unit tests due to timeslice shift to UTC timezone based.
[BZ 1161806] Update the migration code to handle cases where the data spans a DST change. Without this change, the code will not be able to properly retreive indexes that if the start date is before the DST transition and end date is after the DST transition.
[BZ 1160775] - RFE Adding a way to show/hide RHQ subsystems in UI

Current UI is overcomplicated. RHQ does lots of things and
different users use it for different purposes. Although many
subsystems are interconnected and may depend on each other
(e.g. metrics and alerts). This is not the case for all of them
and in the sake of simplicity some of them could be hidden in
UI if user wants to.

This PR allows to hide following subsystems/features in UI:
 * content
 * reports
 * administration
 * events
 * operations
 * alerts
 * config
 * drift

NOTE: This change is only about hiding it in UI, the subsystems
are still working and can be acessed via REST, CLI or direct
URL.

The subsystems can be shown/hidden on the user page
${host}/coregui/#Administration/Security/Users/${userId}
and this information is saved to the user preferences.

It is orthogonal to the access rights that are specified for
roles. Each user may decide what to hide to make the UI
cleaner for him/her.
[BZ 1160775] - RFE Adding a way to show/hide RHQ subsystems in UI - fixing FF issues and changing the switches according to UX proposal
[BZ 1160775] - RFE Adding a way to show/hide RHQ subsystems in UI - i18n and improving CSS for the switches