[1079027] Storage Node (un)deployment can cause deadlock in rhq_storage_node table
Initial commit that attempts to remove umbrella transactions starting at
many entry points, such that scheduling operations happens in their own
trans context.  Needs review and testing...
Transaction delimiters have been updatedin StorageNode beans to try and prevent
db-locking issues.  This caused a problem for storage node deployment
during mergeInventory, because it relied on an umbrella transaction providing
a persisted (but not yet committed) Resource.

Added a general mechanism for performing post-commit actions on newly
merged resources and leveraged it to perform linking a StorageNode to a
Resource.
Make sure StorageNode is committed before we try and deploy it.
More changes to LinkStorageNode to try and get the transactioning right.
[1079027] Storage Node (un)deployment can cause deadlock in rhq_storage_node table
Fix issue with new transactioning that left some entity changes uncommitted.
Merge branch 'jshaughn/storage'

Conflicts:
	modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/cloud/StorageNodeManagerBean.java