AMQP transport with transformer=jms strips query parameters from prorperties.to and properties.replyTo

If amqp message has query parameters in `properties.to` (for example, my_dest?foo=bar), then `InboundTransformer `creates ActiveMQ destination with `physicalName=my_dest` and `options `containing `foo=bar`. The `JMSMappingOutboundTransformer `then populates `properties.to` with `qualifiedName `(that is incorrect also, should be `physicalName`) without options.

It makes imposible to adopt [amqp 1.0 addressing](https://docs.oasis-open.org/amqp/addressing/v1.0/addressing-v1.0.html).

Start by tracing the AMQP path through InboundTransformer and JMSMappingOutboundTransformer. Reproduce a message whose properties.to or properties.replyTo includes query parameters such as my_dest?foo=bar, then inspect how the ActiveMQ destination name and options are mapped. Done means the outbound properties preserve the physical destination name and its query parameters so AMQP 1.0 addressing works.

Written by the indexing model from the issue text.