[BZ 1069691] (JON3-25, PRODMGT-368) DomainDeployments should be managed in a
single menu option in domain mode

Deploymet resource has been removed from Server-Group level. Now we have
only DomainDeployment (living under DC) and Deployment (discovered under
ManagedServer). We manage everything related to ServerGroups within
DomainDeployment's configuration and operations. Operation 'promote' remains
(although not needed anymore)

To assign DomainDeployment with Server-Group user adds new Configuration map
item, select SG, runtime-name and enabled/disabled state.

To enable/disable deployment on given SG user edits particular configite and
changes enabled boolean attribute

To remove DomainDeployment from SG user just removes given map item.

Given domain deployment cannot be assigned to same server group more than
once (even with different runtime-name) - EAP restriction. runtime-name
cannot be changed on existing map items (it's documented and ignored)

New operation for DomainDeployment resource called 'restart' was introduced.
User can restart deployment in particular SG or in all assigned SGs.

DomainDeplooyment's getAvailability() was also changed to return MISSING
instead of DOWN when deployment is not found on EAP.

DomainDeployments get discovered only under master DomainController, not
slave HostControllers
[1079225] Graphs of sub-level resources in groups fail
API's dealing with Resource Groups should typically handle all 3 types of
resource groups: standard, autogroup and autoclusters.  The way to do this
is to use an EntityContext in the API.  In this case we were ignoring
autoclusters.  This fix converts a few group-related APIs to use
EntityContext. It simplifies the APIs, fixes this bug and likely fixes
a few other problems.
[552112] Add time column to Suspect Metrics page
A 4 year old request but still useful, and we aim to please.
fix test failures
new MenuBarView styling
Itest for logging in without a role.
[BZ 1101770,1101773] make sure we do not process agent commands
fix test failure
some minor code cleanup
on HosctController component hold info if given HC is DC as well

This value is updated on component start and also by availability code, when
going from DOWN to UP (to handle cases, when HC was reconfigured to DC)
Access to HC Component property is synchronized, because value is updated by
avail code and can read by discovery code
[BZ 1069545] - addendum to subcategory work
When removing tables from our schema those obsolete tables must be added to
obsolete-schema.xml in order to properly support db overwrite.
- This should also fix test failures resulting from this omission in the
  original work.
Merge pull request #40 from lzoubek/feature/JON3-25

[BZ 1069691] (JON3-25, PRODMGT-368) DomainDeployments should be managed in a single menu option in domain mode
[BZ 1015706,1092756] check for invalid max and update it with the avg

We also log a warning to indicate that we have come across an invalid metric.
We then update and persist the max.

Conflicts:
	modules/enterprise/server/server-metrics/src/main/java/org/rhq/server/metrics/MetricsServer.java
Remove protection from weird metrics like avg > high or avg < low now that BZ1015706, and BZ1092756 are fixed.
Looks like I had already removed the high value check but still had the low value check in place.
[1103375] Viewing operation details for operations with no results throws uncaught exception in GUI
- Handled cases where null results are returned from an operation excecution.
- Fixed one op history update path where [results] data could be lost.
make sure we drop the legacy metrics_index table during schema update

The metrics_index table wasn't getting dropped for new installs. Fixing this
created a problem in TopologyManager where it sets gc_grace_seconds for each of
the tables. This commit modifies the logic in TopologyManager as well so that
it no longer tries to update gc_grace_seconds for metrics_index and so that it
does set it for metrics_cache and metrics_cache_index.
[BZ 1104916] add logic for reducing cluster size from > 4 nodes

The case for the previous cluster size > 4 was missing which resulted in an
IllegalStateException, which in turns causes the undeploy process to fail.