Update Summary metric portlet graphs for Date/Time range feedback of period being selected for charting.
[BZ 1012589]  Multi-line Graph Auto-refresh not working.
Fix an issue where the storage client init was using system properties
to get the storage user and password.  This had two issues:
1) at install the system properties were seeded in AS via
-p rhq-server.properties, but this was prior to the generation of the
storage cluster creds.
2) for HA installs the props file was actually not even correct, the
generated values were superseded by the existing db creds.

This commit syncs the props file and the db, during install, so problem
2 really should no longer be a problem.  But this was mainly done to
reduce confusion for a person who may have wondered why the db and props
file had different values.  It didn't solve problem 1.  To solve problem
1 the storage client should always get its creds from the DB, which it
now does.
 BZ 1010841 - a few more storage client changes.
 fix compilation failure.
Bug 1013489 - It is not possible to download an agent from RHQ server (HTTP Status 404)

Fixed 'Downloads' page broken links
api checks: reverting a change that broke JON 3.2 backward compatibility
(Almost) regain back-compat with RHQ 4.4.0 in script bindings.
Adding intentional api changes for the new methods ported over from RHQ 4.4.0.
[BZ 873866] - Minimizing API changes between JON 3.1.2.GA and JON 3.2.0.GA.

Bug 888927 changed the signature of the
AlertConditionAvailabilityCategoryComposite class to add a missing
parameter.

While the chances of anyone using this method miniscule, we need to retain
the back-compat. Therefore I added the wrong constructor back with
a deprecation notice.
[BZ 873866] - Minimizing API changes between JON 3.1.2.GA and JON 3.2.0.GA.

Commit a4b78eb6e1adeffaa519115a9ef07b3f00025168 fixed the handling of the
server status, but changed the signature of
o.r.c.d.cloud.Server#clearStatus() method in an incompatible way. Adding
the old method back with a deprecation notice.

The chances of anyone using this method are miniscule but we need to retain
back-compat.
[BZ 873866] - Minimizing API changes between JON 3.1.2.GA and JON 3.2.0.GA.

Commit 85f75e0 removed 2 enum fields from the server details, because they
are no longer used due to our move from DB to Cassandra for metric storage.

Nevertheless the clients might be using those fields to get back that
information. To retain the backwards compatibility, we need to keep those
enum fields, making the server details work without recompilation.
The server details will no longer contain any information for the for those
fields. The fact that some information might be missing is part of the
contract of the ServerDetails class though, so the users should be able to
handle that situation.
[BZ 873866] - Minimizing API changes between JON 3.1.2.GA and JON 3.2.0.GA.

The fix for bug 1000006 declared the constructor of
o.r.c.d.configuration.ConfigurationUtility private. It previously had the
default pulic constructor and hence this was a API breaking change.

While the utility class should have had the private constructor in first
place, we cannot break the API, so the public constructor has been
re-introduced with a deprecation notice.
[BZ 873866] - Minimizing API changes between JON 3.1.2.GA and JON 3.2.0.GA.

The fix for bug 840512 changed the way we handle the value of an obfuscated
property, which rendered the obfuscate() method unused. It has been removed
which unfortunately is an API breaking change due to its protected
visibility.

While the chances of anyone using that method are miniscule we cannot break
the API. The method was re-introduced but made a NOOP so that it doesn't
break the obfuscation. The deprecation notice on the method suggests to
stop using it.
[BZ 873866] - Minimizing API changes between JON 3.1.2.GA and JON 3.2.0.GA.

Commit 26959a31d8c37bcb86dc6a845b5707a277bff3cb made the constructor of
the DatabaseQueryUtility private, which it should be, and removed an
unused class.

While the chances of anyone either instantiating the utility class or using
the absolutely useless DatabaseQueryUtility.StatementParameter are very
slim, we need to keep API back-compat.

The public constructor and the class have been reintroduced with
a deprecation notice.
[BZ 873866] - Minimizing API changes between JON 3.1.2.GA and JON 3.2.0.GA.
[BZ 873866] - Minimizing API changes between JON 3.1.2.GA and JON 3.2.0.GA.

Commit 0ba8c5f (among other things) removed several public constants in
MeasurementScheduleCriteria because they were improperly named and didn't
do what they seemed to.

Users might be using those constants even if they don't do what they're
supposed to. The constants have therefore been re-introduced with a
deprecation notice.
api checks: adding the change as a intentional change not to break JON compatibility.
numerous changes in metrics-simulator to simplify things

Metrics are now captured using the Metrics Core library which renders both
Stats.java and StatsCollector.java obsolete.

MetricsCollector has been simplified substantially. It is now seeded with a
starting schedule id and a batch size and generates batch size inserts each
time it runs.

A good bit of the simulator configuration that is specified in the json file
has been removed as well in an effort to make sure things are correct. As of
now intervals and time slices are fixed.

* raw data --> 1 minute
* 1 hour data --> 6 minutes
* 6 hour data --> 1 hour

This means that a day's worth of data is generated in one hour. Minor changes
have been made in MetricsServer to allow for configurable time slices.
allow for configurable time slices
fixing bugs and adding support for compressed time slices

The simulator now uses hard-coded TTLs and time slices. The duration of the
time slice for each table is as follows,

raw data --> 2.5 minutes
1 hr data --> 15 minutes
6 hr data --> 1 hour

Aggregation runs every 2.5 minutes. The execution time for aggregation can and
will exceed 2.5 minutes. I do not want the aggregator thread to block and wind
up kicking aggregation with the wrong start times. It now submits a task for
each aggregation so that the aggregator thread itself does not get delayed.