[[WFLY-3493] Do not remove a JMS resource with deployed dependencies

Ensure that there is a dependency between the JMS resource service
(JMSQueueService and JMSTopicService) and the BinderService for their
JNDI bindings so that if the resource is removed, the missing dependency
is detected.

Add recovering of the JMSQueue and JMSTopic services in the :remove
operations by replaying the runtime part of their corresponding :add
operations.

JIRA: https://issues.jboss.org/browse/WFLY-3493
Optimize cache key size by using component name instead of bean class name.
Merge pull request #6405 from jmesnil/WFLY-3493_remove_queue_with_deployed_dependencies

[[WFLY-3493] Do not remove a JMS resource with deployed dependencies
Merge pull request #6424 from pferraro/ejb

Optimize cache key size by using component name instead of bean class name
[WFLY-547] track uncleanly unregistered slave hosts
WFLY-3440 Split up Java EE dependency processor into the appropriate subsystems