Revert "Revert "[WFLY-2047] org.jboss.as.connector module needs sun.jdk module dependency""

This fix is harmless, even if not strictly "correct", and it solves real-world problems.  There was no good reason to revert this commit in the first place.

This reverts commit 9a3b000767c018a681a4858a84aae20a0b8c7310.
The original revert reverted 88756ddb1061660cb.
WFLY-2665 Make JPA statistics enabling config consistent with other WF subsystems by bringing jipijapa 1.0.1.CR1 in with JIPI-28
[WFLY-2779] Update documentation for "connector" in mod_cluster subsystem
[WFLY-2799] Drop SystemMemoryUsageLoadMetric from mod_cluster subsystem
[WFLY-2747][WFLY-2754] Make audit log facility and appName configurable in the management API
added relative-to attribute to vault element in jboss-cli.xml (related to https://issues.jboss.org/browse/WFLY-2636 cli should be able to use the vault to encrypt a keystore password)
Injection of optional-attribute-name
[WFLY-1555] Upgrade log4j-jboss-logmanager
WFLY-2804 Add -u and -p shortcuts to jboss-cli
WFLY-2804 Add -u and -p shortcuts to jboss-cli
WFLY-1801 Move remoting to use io subsystem for workers

- fix worker defaults
- preserve backward compatibilty
[WFLY-2672] Add TRACE logging for LDAP group loading.
Upgrade to HAL 2.1.1.Final
WFLY-2829 Optimistic locking w/write skew check requires versioning to be enabled
[WFLY-1597] / [WFLY-2208] Ensure that any HTTP to HTTPS redirect occurs BEFORE upgrade.

That is if the HTTP interface is configured with a secure port we do not support any unencrypted management access.
Don't modify the top level deployment's module spec from a sub deployment
[WFLY-1597] / [WFLY-2208] Handle a redirect from HTTP to HTTPS and convert to the correct address format for https-remoting.
WFLY-2819 Upgrade jsf-impl to 2.2.5-jbossorg-3
[WFLY-2759] Upgrade to HornetQ 2.4.1.Final

* upgrade hornetq version to 2.4.1.Final
* add new initial-connect-attempts attribute for cluster-connection and
  bridge resources [WFLY-2758]

JIRA: https://issues.jboss.org/browse/WFLY-2759
JIRA: https://issues.jboss.org/browse/WFLY-2758
[WFLY-2730] HTTP upgrade multiplexing

When the HTTP upgrade handshake is performed, check whether
the http-upgrade-endpoint is defined and accepts the handshake
only if its value matches the acceptorName.
This http-upgrade-endpoint header is used by a http-connector to
specify which http-acceptor must be used in case there are multiple
http-acceptors registered on the server.

If the http-upgrade-endpoint header is not present, the 1st http-acceptor
encountered will be used. This is not deterministic and is suitable only
if there is a single http-acceptor.

* remove native messaging port for messaging subsystem.xml configuration
and use http-connector for JMS RemoteConnectionFactory
* add a http-connector-throughput to replace the corresponding
  netty-throughput

JIRA: https://issues.jboss.org/browse/WFLY-2730