[WFLY-4013] messaging's socket-binding are not registered

When the HornetQService is started (resp. stopped), the socket-bindings
used by the service are registered (resp. unregistered), so that their
runtime state is correct (calling :read-resource on them will display
them as bound).

Note that the socket-bindings referenced by the connectors are *not*
registered. We use them only to get a reference on the host/port of the
server but they are not opened (the client will open them).

JIRA: https://issues.jboss.org/browse/WFLY-4013
Merge pull request #7004 from jmesnil/WFLY-4013_messaging_socket_binding_registration

[WFLY-4013] messaging's socket-binding are not registered
[WFLY-4139] Allow batch to start without CDI.

The batch subsystem no longer requires a bean manager to start.
Validation that a transaction manager is present is now performed on
subsystem startup rather than at runtime. Non-CDI deployments can now
use batch, as can deployments that do not start jobs.