Without these permissions, it is impossible to use anything but the Artemis
Core protocol to conduct RPC calls, since Artemis only allows either:

a) non-durable queues with a random (UUID) name
b) durable queues with fixed name

to be created.

For AMQP queues, Artemis prefixes the replyTo address with 'queue://',
but it doesn't do the same for the BINDING_ADDED notification. Strip
the prefix from the replyTo name to make sure the queueing logic
in RPCServer works as expected.

When converting Core messages to AMQP, Artemis converts the message
payload as a string value by default. Corda RPC responses are binary,
and they are not prefixed with their length as strings are.

# Conflicts:
#	node/src/integration-test/kotlin/net/corda/node/NodeRPCTests.kt

Make it compile to start with and make Detekt happier.

Test currently fails as authentication credentials not properly passed via JMS.

Next blocker: No permissions to create the queue

Next blocker: No permissions to send
Interestingly, there is a test net.corda.services.messaging.MQSecurityAsRPCTest which is precisely asserts that an attacker cannot do things we are trying to do by using internal ActiveMQ API.

    Currently blocked by:
    ```
    Identifier contains invalid JMS identifier character '-': 'rpc-id'
    java.lang.IllegalArgumentException: Identifier contains invalid JMS identifier character '-': 'rpc-id'
    	at org.apache.qpid.jms.message.JmsMessagePropertySupport.checkIdentifierLetterAndDigitRequirements(JmsMessagePropertySupport.java:101)
    	at org.apache.qpid.jms.message.JmsMessagePropertySupport.checkPropertyNameIsValid(JmsMessagePropertySupport.java:63)
    	at org.apache.qpid.jms.message.JmsMessagePropertyIntercepter.setProperty(JmsMessagePropertyIntercepter.java:724)
    	at org.apache.qpid.jms.message.JmsMessage.setObjectProperty(JmsMessage.java:348)
    	at org.apache.qpid.jms.message.JmsMessage.setStringProperty(JmsMessage.java:433)
    	at net.corda.node.amqp.jms.AmqpRpcTests$Companion.mapTo(AmqpRpcTests.kt:52)
    	at net.corda.node.amqp.jms.AmqpRpcTests$Companion.mapTo(AmqpRpcTests.kt:47)
    	at net.corda.node.amqp.jms.AmqpRpcTests$Companion.access$mapTo(AmqpRpcTests.kt:35)
    	at net.corda.node.amqp.jms.AmqpRpcTests$RPC over AMQP$1.invoke(AmqpRpcTests.kt:84)
    	at net.corda.node.amqp.jms.AmqpRpcTests$RPC over AMQP$1.invoke(AmqpRpcTests.kt:33)
    	at net.corda.testing.node.internal.DriverDSLImplKt.genericDriver(DriverDSLImpl.kt:1199)
    	at net.corda.testing.driver.Driver.driver(Driver.kt:185)
    	at net.corda.node.amqp.jms.AmqpRpcTests.RPC over AMQP(AmqpRpcTests.kt:59)
    	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    	at java.lang.reflect.Method.invoke(Method.java:498)
    	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
    	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
    	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
    	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
    	at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
    	at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
    	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    	at java.lang.Thread.run(Thread.java:748)
    ```

… changes for JMS call to go through