[BZ 962886] throw console errors when LDAP server is enabled, but not reachable.

Conflicts:

	modules/enterprise/gui/coregui/src/main/resources/org/rhq/coregui/client/Messages_de.properties
	modules/enterprise/gui/coregui/src/main/resources/org/rhq/coregui/client/Messages_ja.properties
[1139735]
Add undo of the storage node version stamping in case of an upgrade failure
invoking undo logic.   The current thinking is that this is not necessary for
the server stamp since it happens at the end of server upgrade.

Also, deprecate the upgrade --start option and make it do nothing if specified.
This is because upgrade is a multi-step process and as such an automatic
start does not make much sense, and more likely will cause problems. Start
should only be done manually, after all upgrade steps are complete.
[BZ 1139735] Storage node schema version should not be attempted to upgrade in case of clean installation
[BZ 1136751] For each iteration of DriftDetector, run all the available drift schedules
Bug 1004977 - Datasource configuration changes SHOULD NOT require a complete reload/restart of EAP

"Enabled" attribute is no longer an editable configuration property (it will still be available on (xa-)datasource creation).
Instead, users will have to use the "Enable"/"Disable" operations.

"Enable"/"Disable" definitions have been changed to include a new "allow-resource-service-restart" property, defaulting to false.
If set to true, the corresponding management request header will be added. This allows to disable/enable a datasource without a server reload.

The datasource component update configuration logic has been enhanced to send only configuration changes. It requires an extra request
to read the current datasource config, but it avoids a server reload or datasource disable/enable cycle if the user only wants to
change a set of properties which do not require it.

Also, a new specific component class has been added for the datasources subsystem resource type. It used to be shared with the (xa-)datasource component.
While in the beginning it probably was easier to have a single class for code sharing between the "Create Child Resource" process and the "Update Configuration Process",
the (xa-)datasource component logic has become quite complex so it's safer to have separate component classes.

Eventually, the plugin descriptor has been updated to document that some (xa-)datasource properties cannot be unset if they already have a value.
Bug 1004977 - Datasource configuration changes SHOULD NOT require a complete reload/restart of EAP

Do not send operation headers if null. This saves bandwith.
Perf: avoid compiling regular expression patterns over and over in AS7 plugin hotspots

Also:
* in VersionedRuntimeDiscovery, fixed a string != string issue
* avoid string concat when working with a stringBuilder (it creates a useless additional builder)
Fix error in logger definition
Remove comment in plugin descriptor saying 'enabled' attribute is read/write and manually managed by datasource component
Updated DatasourceTest to check that:
* changing a property like "max-pool-size" does not require disabling the datasource nor reloading the server
* this sequence does not require reloading the server:
** execute disable operation with restart service header
** configuration update
** execute enable operation