[1092707] If re-install is attempted using a different storage node host name, install fails
Allow a re-install/re-upgrade to replaceme existing storage node definitions
as long as the storage nodes have not actually been used.  Basically, if
none of the storage nodes are yet linked to a resource, they are eligible
for replacement.

(cherry picked from commit a074c1851c7f271e97478625112a1de315ee1bd3)
Signed-off-by: Jay Shaughnessy <jshaughn@redhat.com>
Merge branch 'release/jon3.3.x' of github.com:rhq-project/rhq into release/jon3.3.x
[1155612] upgrade from jon 3.1.2 to jon 3.3.0 er05 does not work
Fix an install issue when upgrading from a BSN (before storage nodes)
version.  Go back to the legacy db-upgrade step that adds the entire
rhq_storage_node table and make it match the same table definition you'd
get from a new db.  Because no SNs existed at upgrade-time the version
column updater never gets a chance to execute. And therefore the insertion
of the initial SN fails.

(cherry picked from commit 0e4c52efca13a54937cdc71d703afa89d681f710)
Signed-off-by: Jay Shaughnessy <jshaughn@redhat.com>