BZ1032192 - AlertCondition composite queries, query each column

Hibernate would return an empty entity and consequently lead to N+1 selects.

The code is ugly, unfortunately.

Adding tests for these queries
BZ1032192 - AlertCondition intentional API changes

Adding intentional API changes as well
[BZ 1069547] Support for API-based bundle handlers

This is to support new type of dedicated bundle handlers able to do more
than just file-system modifications. In order to enable them to e.g.
connect to some remote endpoint, a more complex configuration data needs
to be passed over.

This creates coupling between the bundle destination definition and the
handler that is able to deploy to such destinations (because it needs to be
able to use the configuration offered by the destination definition) but
that is unavoidable given the specific things the handlers would be doing.

* The resource types can use the new "destination-definition" tag under
bundle target to define new type of destinations that can use
a "connection string" expression + can pass all or parts of resource or
plugin configs or traits to the bundle handler.

* The agent-side bundle handlers have access to the bundle deployment
configuration even in the purge scenario. This is to support the more
complex bundle handlers needing the config to better identify the bundle
deployment.

* The deploy directory is no longer a required argument when creating a
bundle destination. This is because for the API based bundle handlers,
such configuration property might not make any sense and would only create
confusion on the user side.

* It is no longer required for the server bundle plugins to come up with
the full list of the required files upon reading the recipe alone.
The bundle plugins can therefore choose whether they support piece-wise
upload of the bundle version or only support uploading a full bundle
distribution file.
[BZ 1069547] Wildfly patching by various means

* Bundles - using a dedicated bundle type. This enables us to understand
the patch zip file as our bundle without any RHQ specific recipe.
We can supply various parameters to patch application process but although
revert is supported, it cannot be configured by any parameters as one can
do over Wfly's CLI.

* Content - patches appear as packages of the AS7 standalone server.
They are discoverable and can be installed from repositories (without any
possibility of customizing the install process). Delete (i.e. rollback)
is supported, again without configuration.

* Rollback through operation - in case user would need special behavior
on rollback, they can use a dedicated operation on the AS7 standalone
server resource.

* Bundle handover - patches can be installed using the bundle handover
facility, too, using the "patch" action. This is configurable using
handover parameters and supports all the parameters available in Wfly's
CLI.
updated check boxes to follow patternfly theme
Update table Filter/Header to better reflect patternfly l&f
See - https://www.patternfly.org/widgets/#data-tables

EnhancedSearch bar has 'search' button removed. Search picklist should just work as you type or reset focus, without needing to manually select button
[BZ 1069547] Fixes

* typo in CliExecutor.executeCliCommand preventing execution in
connected mode

* apply patches in disconnected mode when deploying through content
subsystem
Bug 1053483 - RHQ Admin UI references 'Cassandra' rather than storage node

Cassandra Server JVM resources renamed to JVM
Merge branch 'master' of git://github.com/rhq-project/rhq into patternflyTable

imerging
[BZ 1059444] Add attempted hostname to the port in use error messsage
Changes to button structure with an added icon throw off the CSS selector for primary and destructive buttons.
PFly has no notion of images in buttons, so removing the images fixes the color
[1118091] RHQ Agent resources are not being auto-clustered in resource group due to their unique resource keys
To enable good autoclustering of RHQ Agent resources across platforms the
agent resource keys must be the same.  In general each platform has at most
one imported 'RHQ Agent' child resource and it is named the same as the
platform (Actually the platform's resource key). In this case do not
incorporate the agent name into the resource key.  In that way we can have
a generic static reskey for the agents, across platforms, while still
maintaining unique agent names across all agents (an RHQ requirement).  In
the rare case that a platform has multiple agents deployed (typically a
perftest scenario, but sometimes a production scenario) at most one agent
will get assigned the static key, only the one whose name matches the
parent.  All others will get the *predictable* legacy keys we've used up to
this point.  So, in the vast majority of cases, we should see good
auto-clustering of the rhq agents.
Added missing files.  I suspect most of these aren't ever used, just automatically loaded, but can't see where.
upgrade to Cassandra 1.2.18
[BZ 1118063] Use resourceKey as columnFamilyname on operations and set SimpleValue name when discovering columnFamily resources
BZ 1118906 - support upgrading the agent via rhqctl when the install location is being referenced by a symlink
Merge branch 'master' of git://github.com/rhq-project/rhq into checkBoxes

merging
[BZ 1118063] Add unit test to check for proper ResourceKey parsing
Merge pull request #88 from jsanda/cassandra-1.2.18-upgrade

Upgrade to Cassandra 1.2.18
Merge pull request #87 from alns/BZ1118926-MissingIcons

BZ1118926 Added missing files.  I suspect most of these aren't ever used, just automatically loaded, but can't see where. + utilizing the new progressbar when navigating through resource tree (before the spinner was displayed directly in the resource tree which led to tree component moving up and down)