add request controller subsystem to web feature pack standalone config
Upgrade Weld to 2.2.7.Final
[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-4140 In some case :activare on resource-adapter fails if id != archive_name
WFLY-4145: Upgrade HAL to 2.5.0.Final
Merge pull request #7009 from hpehl/WFLY-4145
Merge pull request #7007 from maeste/WFLY-4140
Merge pull request #7000 from jharting/weld227Final
Merge pull request #6965 from emmartins/web-feature-pack-subsystems-fix
[WFLY-4130] Allow -secmgr to be used with the appclient to enable the security manager.
Merge pull request #7012 from jamezp/WFLY-4130

[WFLY-4130] Allow -secmgr to be used with the appclient to enable the security manager
WFLY-3916: removing custom runtime permissions