[1139735] HA upgrade issues with storage cluster schema change
First check-in for the necessary revisions. What makes a storage cluster
schema change difficult is that it requires the entire storage cluster to
be upgraded to the new bits, and to be running, in order to apply the changes.
This runs contrary to our typical upgrade approach which is to shut
everything down and upgrade one install at a time (an install being a
server and/or storage node).  The basic  approach is to now track the
install version for each installed component, and only when evrything has
been upgraded, then do we allow the storage cluster start and then perform
the schema update as a separate upgrade step.
- Add version stamp on rhq_server and rhq_storage_node
- Add db upgrade logic to add fields and init them to the current version
- Add Support to stamp the version on install and upgrades
  - includes updates to jboss modules, rhqctl and installers
  - includes ability to contact RDB from storage installer
- Add --storage-schema and --list-versions coptions to rhqctl upgrade
- Stop server startup unless topology is set to homogenous version, to prevent
  running an environment that is not completely upgraded.

-
 [BZ 1078546] Relax remote client version check so that patched but non-breaking api changes accepted.
 [BZ 1081564] Update rhq ui to support patch update increments when available."
  Modify jboss-as-dmr-client to be patchable.

Conflicts:

	pom.xml
 Add support for incremental pom versioning for dependencies.
 Update rhq-core-domain for independent versioning as well.
 A few more updates for independent versioning of rhq-core-domain as used in many places.
 - user project.parent.version instead as this will not change.
 Update rhq-enterprise-jar for independent versioning.
 A few more updates for rhq-core-native-system and version documentation.
 Updare rhq-core-plugin-api for independent versioning.
 Update rhq-core-util for independent versioning.
 Modify rhq-remoting-client-api for independent versioning.
 A few more changes for rhq-remoting-client-api.
 Missed two references for rhq-core-util independent versioning.
 Root pom should still use project.version
 Add independent versioning for script and platform modules.
 Update test code to be more flexible in test artifact resolution.
 Modify rhq-installer-util, rhq-server-control and rhq-server-metrics for independent versioning.
 Increment module versions for productization and Update 02.
 Modify rhq-database-plugin and rhq-postgres-plugin for independent versioning.