[1100300] Update of a resource configuration sometimes takes more then 100 seconds
Initial commit for this.  Try to chunk work such that we don't perfrom
complete scans at large intervals, but smaller, partial scans at
more frequent  intervals.
- Add two new agent config props to assist in configuring the process.
[1100300] Update of a resource configuration sometimes takes more then 100 seconds
Given feedback from the github pull request (62), change things around
to support tighter time controls at the expense of some more memory and
complexity.
- remove the 750ms delay between checks. This was supposed to be removed in
  the first pass of changes. Slows things down in a major way, the chunking
  should keep runtime spikes in check.
- increase check frequency to every 2 minutes but drop to 10s limit on
  runtime.  Now that the 750ms delay is gone, I ran a check of the 3 RHQ
  roots (EAP server, agent, storage) in well under 3s.  The time a
  root and its members are again eligible for a check is still 1 hour
  from the time it completes it's prior check (meaning it's last child
  is checked).

TODO: Still have to update logging to DEBUG once everything else is
      cleared.
  on a specific root
[BZ 1100432] Increase the availability operation timeout to 15 minutes. Due to changes in availability (now always async) the implementation is simpler for current code base then the past where async was a special case.

The 15 minutes give ample time for the server to reply to plugin request. Anything bigger than this timeout would help the avail checking and the server should be marked down.
[BZ 1100432] Reduce the timeout period to 10 minutes to be more in line with new async avail thread limits.
[BZ 1100432] Reduce the http timeout 1 minute to match server async timeout.

Add heuristics to report the server DOWN after a 5 minutes of http timeouts. And mark all the resources that have the availability request time out as UNKNOWN to defer to previous reading.
[BZ 1100432] Make log instances available locally.
[BZ 1105269] Switch to ReadResource to avoid false positives from missing deployments.
[BZ 961294] Expose config file option to the config mode for the wrapper script.
[BZ 961294] Move clean config option to the wrapper sh. The ec2 wrapper was using this option in an unreliable mode and could have resulted in errors in the wrapper or agent.
[BZ 961294] Add missing options to the help line.
Bug 1102562 - [eap6] Make DomainController's Domain name configurable

Domain Name is now part of resourceConfiguration for DomainController and
HostController resources. Only DC's are allowed to change this configuration
(handled by EAP). As 'Domain Name' is not available (and known) from EAP
admin console, there's a high chance it's unconfigured (having default value
'Unnamed domain').
update stuff required for restApi itests to pass
[BZ 1082806] - Context referrals are hardcoded to ignore in LDAP configuration - making 'follow referrals' optionally configurable in system settings
fix context-menu separator style (disabled in patternfly.css)
JBossAS7: export "Domain Name" as a trait

We need this in order to have dynagroup definitions composed from Domain
Name + some other configuration property. Also, this property is called
'name' on HC, but in RHQ we call it 'domain-name' - this is because
dynagroup evaluator is not strict when it comes to trait names - so having
resource.trait[name] includes several traits.
[BZ 1099854] [BZ 1097698]- [as7] Incorrect expression in pre-defined

Provided expressions fixed - now taking into account domain-name trait.

Managed Servers in domain : now generates groups per domain-name = set of
all managed servers on all hostrcontrollers grouped by domain-name

Managed Servers in server-group: now generates sets grouped by domain-name
and server-group name.

I also fixed provided expression called 'Deployments in server-group' -
which was relying on Deployment resources under server-groups (recently
removed)
Introducing API checking to agent-server comms.
[BZ 1096902] - "Maximum" and "Minimum" values do not match the graph values - fixing a race condition in CustomDateRangeState
[BZ 1082806] - Context referrals are hardcoded to ignore in LDAP configuration - making sure the dbupgrade won't fail if the value is already present in the DB
[1110277] RHQ_EVENT table's detail field limit of 4000 character will break when a log message contains multibyte characters (UTF-8)
This is a problem in a few places, not just events.  We're not
properly protecting against the 4000 byte limit on oracle, just
the 4000 character limit declared on the varchar2 field.
- Add DatabaseType.getString() which can truncate as needed in
  a vendor-specific way.
- Use the new getString() to store safe versions of event detail,
  alert notification log message, and calltime dataset destination.