WFLY-2422 Remoting profiles

Adds remoting profiles to ejb3 subsystem. Profiles consist of remote ejb receivers and local ejb receiver. Profile is represented by RemotingProfileService which depends on all connection services that ejb receivers need to connect to. If client wants to use remoting profile it can configure it in jboss-ejb-client.xml.
To provide backward compatibility client can still define remoting ejb receivers directly in jboss-ejb-client.xml. In this case during application deployment internal profile service, which consist of those receivers, is created. Remoting-profiles are responsive to cli operations: each time profile resource (or any of it's children resources) changes profile service is being restarted with new configuration. In case of invalid configuration update (f.e.  non-existent connection dependency) operation is being rolled back and profile is restored to it's last correct configuration.
What exceptions are caught here?

Only throw OFE if it meets the criteria discussed at the OFE class javadoc:

https://github.com/wildfly/wildfly-core/blob/master/controller/src/main/java/org/jboss/as/controller/OperationFailedException.java#L28

For other failures that indicate some sort of server fault, throw a RuntimeException.

Don't wrap one OFE (e.g. from createChannelOptionMap) in another.

If you are constructing an OFE with a string message, prefer the constructor that takes a String over the deprecated one that takes a ModelNode.