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.
Merge pull request #104 from lzoubek/bugs/1122444

Bug 1122444 - Server responds with 204 even if it fails to find the sche...