Define a galleon layer for transactions

This layer would add some benefits:
1) Avoid duplication of permissions we are observing with feature-groups in a cloud-profile context.
2) Allow extension in other context. For example, transactions layer could be redefined in order to enable tx-recovery (add node-identifier=${jboss.node.name} and recovery-listener=true attributes added to the subsystem) and package needed JBOSS modules (eg: tooling for tx-recovery).