fix upgrade test failures

The problem is in set up code on upgrade testing. There is no change to
production code.
[BZ 1108095] fix compiler errors
[BZ 1070262] Updates to the configuration upgrade code for the server and the agent.

This commit resolves the upgrade obfuscation for rhq-server.properties file and some minor tweaks for the agent-configuration.xml file.
[BZ 1075575] Upgrade the C* driver to a version that depends only on C* server version 1.2.18-jboss-1.
[BZ 1070262] Snip superfluous "public" access modifier.
[BZ 1070262] Obfuscate properties in agent-configuration.xml when the file originates from older agents.
[BZ 970784] Fix GUE on new deployments
Bug 1146583 - "Ignore" button is disabled always under "Discovery Queue"

Previous logic of enabling/disabling "Ignore" button tried to prevent
situation, that user could ignore a NEW platform and/or it's child. Previous
logic would not work in case user also selected at least another resource
that "could" be ignored (a child of imported platform).

Now user can ignore MEW platform as well or it's child. If platform is
IGNORED it's not possible (at least from UI) to import it's NEW children.
Bug 1122444 - Server responds with 204 even if it fails to find the schedule
upon POST /metric/data/raw request

As POST /metric/data/raw accepts data points for various schedule IDs
rejecting all data, just because several have invalid scheduleId may not be
a good idea. Current fix does:
 * return 204 (No content) in case all scheduleIds are valid and all data
were accepted
 * returns 201 (rejected data) in case some data points were rejected and
some accepted
 * returns 403 (rejected data) in case all data points were rejected

This commit also fixes endpoint POST /metric/data/raw/{resourceId} which now
returns 403 in case there is at least 1 non-existing metric for given
resource ID (this case was previously failing on NPE)
Bug 1122444 - Server responds with 204 even if it fails to find the schedule

Get ISPN cache to work correctly for REST:

REST api was using incorrect cache name - so used cache was not
preconfigured at all, thatswhy cache entries never expired. Now, we'll
deploy rhqRestCache which is preconfigured with lifespan=15m and
max-idle=5min. This means, cache entry will be dropped and refreshed every
15minutes no matter how often is accessed and also if not accessed for
longer than 5minutes.