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
Merge pull request #65 from genman/BZ1032192

BZ1032192 - AlertCondition composite queries, query each column
[BZ 1070257 + BZ 911432] - Increasing the size of db column RHQ_ALERT_CONDITION_LOG and adding an explicit way to match alert condition on event source

messages from squashed commits:
* [BZ 1070257 + BZ 911432] - UI for alert definitions of type Event Detection and the ability to match on a source location regular expression.
* [BZ 1070257 + BZ 911432] - i18n
* [BZ 1070257 + BZ 911432] - There was a change in public constant in core/domain -> adding it as intentional api change
* [BZ 1070257 + BZ 911432] - rhq_alert_condition_log.value: VARCHAR2(512) -> VARCHAR2(4000); fixing the situation when one or both regular expressions are empty (getValueAsString() returns 'null' as a string if the form field is blank - http://forums.smartclient.com/showthread.php?t=21516)
[BZ 1070257 + BZ 911432] - ensuring the value passed to AlertConditionLog.setValue satisfies the db constraint (for Postgres it is AlertConditionLog.MAX_LOG_LENGTH chars and for Oracle AlertConditionLog.MAX_LOG_LENGTH bytes).
[1070257] (JON3-36) Extend length of Details field of alert notifications
One additional commit to the PR.  Just use DatabaseTypeFactory.getDefaultDatabaseType()
instead of figuring it out manually.
[BZ 1069547] Fix tag manager bean itests. BundleManager is now more strict
about destination specifications.
Fix db-upgrade.xml due to bad merge.
Fix test failure due to API change.
[790101] - as5 plugin: warnings should not be logged for AS/EAP versions that do not require the corresponding jar
I changed the offensive WARN-level message to DEBUG level.  It's not really
possible to distinguish between non-existent and non-readable, or to know
which versions require which JAR.  If there is a failure then we can turn
on debug to see the message.
Bug 1128614 - RHQ 4.12 high CPU usage in hibernate thread (java.util.regex.Pattern$Start.match)

EAP up to 6.3 included has an issue with the JIPI implementation which cause high CPU usage when reading the Hibernate Persistence Unit with :read-resource.

High CPU usage was detected when checking for availability and loading configuration. So the fix consists in:

* BaseComponent#getAvailability change
Read only minimum information as we just want to make sure we can read the resource. There's no need to read the children names, evaluate defaults, and retrieve runtime attributes.

* HibernatePersistenceUnitComponent#loadConfiguration addition
Reading the "enabled" attribute is the only thing needed.

These changes not only fix the issue but generally improve performance in the AS7 plugin (less data sent over the AS7 management connection).