[BZ 958922] RFE: support for passing plugin config when creating child
resources

Now we support all 4 possible 'ways' to create a resource on RHQ

1. regular resource (was already implemented) - when REST client create
resources that agent would have discovered. Such resources is not possible
to create via UI or CLI

2. content-based resources (was already implemented)

3. resource children: similar to content-based resources, UI analogy is
"Create Child". Create child history exists. - possible resource duplicities
are handled on agent side.

4. manual resources: Resources that could be only manually Imported from UI,
create child history does not exist for those, and their resource key highly
depends on given pluginConfiguration (although resourceName can be passed).
Duplicates are handled on server side, since underlying API does not report
an error when manually imported resource already exists.

For 3. and 4. there's client can optinaly pass only required plugin/resource
configurations. In rest api code, we retrieve all the defaults from resource
type and then apply passed values on top.
[BZ 1069679] Expose responseTime metric via rest

callTimes are exposed via endpoint GET /metric/data/{scheduleId}/callTime
supported are both aggregated (default) and 'raw' callTime data. CallTime
values can be pushed via PUT /metric/data/{scheduleId}/callTime. Note that
data retrieved via GET has different format as what is pushed. User pushes
really RAW callTimes (time,callDestination,duration) but he *always*
recieves aggregates.
[BZ 1070668] Incorrect default configuration of RHQDS resource

Installer code fixed to properly fill xa-datasource-class property when
creating RHQDS. Class names for postgres, oracle live as constants in java
class.
added new lines between methods
Merge pull request #14 from lzoubek/bugs/1070668

[BZ 1070668] Incorrect default configuration of RHQDS resource
[1079027] Storage Node (un)deployment can cause deadlock in rhq_storage_node table
Initial commit that attempts to remove umbrella transactions starting at
many entry points, such that scheduling operations happens in their own
trans context.  Needs review and testing...
Setting the scope of SmartGWT dependency as provided, because it is needed only during the GWT compile time.
Running the stopwatch and logging the result only if debug lvl is set.
[BZ 1069688] - (JON3-24) Add alert name filter to "Recent Alerts" dashboard portlet - Filtering now works for dashboard portlet (called "Recent Alerts") as well as for the "Summary/Activity" subtab portlet (called "Resource: Alerts" and "Group: Alerts")
Transaction delimiters have been updatedin StorageNode beans to try and prevent
db-locking issues.  This caused a problem for storage node deployment
during mergeInventory, because it relied on an umbrella transaction providing
a persisted (but not yet committed) Resource.

Added a general mechanism for performing post-commit actions on newly
merged resources and leveraged it to perform linking a StorageNode to a
Resource.
Make sure StorageNode is committed before we try and deploy it.
More changes to LinkStorageNode to try and get the transactioning right.
Merge pull request #13 from lzoubek/bugs/958922

[BZ 958922] RFE: support for passing plugin config when creating child
Merge pull request #5 from lzoubek/bugs/1069679

[BZ 1069679] Expose responseTime metric via rest
[BZ 1075575] Update Cassandra to a version specially crafted to not print the superfluous warning about OpenJDK.
BZ 823965 Maintain existing agent-configuration.xml and log4j.xml files after agent auto-update.
The new configuration will be kept in agent-configuration.xml.new and log4j.xml.new
so that we at least provide the user with the updated defaults in case they want to manually merge them.
BZ_1080171 - defer adding of "WHERE" keyword until we know that it is needed.
[BZ 1070243] - (JON3-31) Add "Recent Events" portlet into JON
Dashboard

To make the filtering (based on resource name) working, I had to add also
 the new method to the EventCriteria class.

To sum it up, it is possible to filter by:
 * time ("from, to" or "last n mins/hours/days")
 * resource name - only for global Recent Alerts portlet; it accepts also a substring of a name
 * event source path - it accepts also a substring of a path
 * severity (almost the same as alert priority filtering)
 * result counts (5 is default)

Having that said, the performance shouldn't be an issue, because the
filters may be set to fetch only a few records.
Updated checks after comments from @metlos.
Merge pull request #17 from pilhuhn/bz1080171

BZ_1080171 - defer adding of "WHERE" keyword until we know that it is needed.