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.
[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.
[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.
BZ 1091128 - Support for object name partial matching like :name=IPCLogger-%a%

Note that suffixes or infixes patterns are not supported.

One possible incompatible change is the ObjectName query will include all
object name properties, e.g. if there is

    a:key=%value%

the ObjectName query used to be

    a:* (and then somehow things would get filtered)

but instead the ObjectName query will be

    a:key=*
Bug 1098092 - It's not possible to query pre-defined dynagroup definitions
via CLI

Added boolean filter parameter to ResourceGroupDefinitionCriteria class - so
group definitions can be filtered for "userDefinedOnly" - which excludes
provided canned expressions.
Bug 1109272 - [as7] Incorrect description of ManagedServerDeployment
[BZ 873471] Token replacement takes into account <property> properties

The ant users are used to defining properties using the standard ant
<property> task. We now recognize such properties when replacing
tokens in the bundle files.

To support <property file="..." /> format, the file in question has
to be defined as a bundle file using rhq:file or rhq:url-file. This
would make it deployed though, which might not be what the bundle
author wants, so a new attribute "deploy" has been added to all the
rhq:file, rhq:archive, rhq:url-file and rhq:url-archive, defaulting
to true, meaning whether to deploy the file/archive or not.

Also, the standard Ant <property> task can now appear inside
rhq:bundle alongside the rhq:input-property.

An example deploy.xml might look like this:

<?xml version="1.0"?>
<project name="property-demo" default="main"
         xmlns:rhq="antlib:org.rhq.bundle">

    <rhq:bundle name="Property loading demo" version="1.0">
      <rhq:input-property name="user.provided"/>
      <property name="bundle.defined" value="xxx"/>
      <property file="in-bundle.properties"/>

      <rhq:deployment-unit name="sample-deployment-unit"
                           compliance="full">
        <rhq:file name="in-bundle.properties" deploy="false"/>
        <rhq:file name="deployed.file" replace="true" />
      </rhq:deployment-unit>
    </rhq:bundle>
    <target name="main"/>
</project>

The deployed.file mentioned above could contain the
@@bundle.defined@@ token which would be replaced with "xxx". It could
also contain tokens with names of any properties defined in the
"in-bundle.properties" file that is supposed to be placed in the
bundle file alongside the deploy.xml.
[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 1070431] Provide initial CSP integration for opening JON cases

Added new WAR deployment containing RHA frontend and JON-specific backend
servlet
Integrate link to RH Access as a "Red Hat Support" button in main bar. For
testing purposes this view is accessible even for RHQ