[WFLY-11360] Manually revert commit 43018d35a98a4c7b5905a048aa99d435eb38a436 "[WFLY-11166] Use the org.wildfly.transactions.local-provider capability and ContextTransactionSynchronizationRegistry instead of direct use of ServiceName constants"

This is not a simple revert as there have been subsequent changes.

This also removes the deprecation of the TxnServices and TransactionSynchronizationRegistryService service name constants. Use of those should still be replaced with some sort of capability, but the WFLY-11166 approach of using ContextTransactionSynchronizationRegistry is currently not correct.

[WFLY-11166] Add an org.wildfly.transactions.iglobal-default-local-provider capability and deprecate external use of the jboss.txn.TransactionManager, jboss.txn.UserTransaction and jboss.txn.TransactionSynchronizationRegistry service names."

[WFLY-11166] Add an org.wildfly.transactions.iglobal-default-local-provider capability and deprecate external use of the jboss.txn.TransactionManager, jboss.txn.UserTransaction and jboss.txn.TransactionSynchronizationRegistry service names."

Change AssociationService and dependents to start LAZYly to retain ClusterTopologyListeners listeners for lifecycle of remoting channel. This isn't ideal, and hopefully temporary, but is sufficient to workaround race conditions between the channel and AssociationService lifecycles.