BZ1094424 - do not reindex tables by default; don't use UNRECOVERABLE

ALTER INDEX {0} REBUILD UNRECOVERABLE

When being run on Oracle, this prevents inserts while the rebuild takes place,
which may be several minutes. This has caused agents to time out and false
alerts to be generated.

Unrecoverable is not a good idea as it locks the table during the calculation:
https://community.oracle.com/thread/1103546?tstart=0

The default should be false, as well UNRECOVERABLE is not a good idea either on
Oracle because of the locking.
[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.
Merge pull request #49 from rhq-project/BZ1100432

[BZ 1100432] Increase the availability operation timeout ...
Merge pull request #52 from rhq-project/BZ961294

Silent configuration via agent wrapper script
[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.
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').
Merge pull request #48 from lzoubek/bugs/1102562

Bug 1102562 - [eap6] Make DomainController's Domain name configurable
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.