Add exchange/routingKey to RabbitMessageSenderContext

[ngocnhan-tran1996]

I see #2814 and I think RabbitMessageSenderContext.java should have field exchange and routingKey.

But I think it's better if we use MessageProperties#setReceivedExchange and MessageProperties#setReceivedRoutingKey instead.

[artembilan]

The setReceivedExchange and setReceivedRoutingKey are for consumer side.
Since there is no options in the org.springframework.amqp.core.Message fro destination properties, we don't have have unless provide them separately.

[artembilan]

Also add your name to the @author list of all the affected classes.
Don't you think that we need to cover the change somehow in the tests?
Or that one is going to be follow up as a fix for the #2814 ?

Thanks

[ngocnhan-tran1996]

This one is going to be follow up as a fix for the #2814

[artembilan]

I guess this will go to TemplateLowCardinalityTags in the next contribution.

[ngocnhan-tran1996]

I think now it's more easier to determine exchange or routing key for doing traces/metrics without splitting / in RabbitMessageSenderContext.

[vmeunier]

@artembilan
I don't think my issue is still worth anything now since the tags were added here. I was actually trying to change this now and ended up checking at the code "it's already done ?! Did I smoke anything ?"

[ngocnhan-tran1996]

@vmeunier

I follow your issue and added field exchange/routingkey. I think it will be easier for you to implement metrics/traces, and IMO it's not done yet.

[vmeunier]

@ngocnhan-tran1996 ok you're right, I don't know why you needed to add those informations, it confused me since I knew I had that stuff to change :)

[artembilan]

I believe the original issue talks about adding something like:

					.and("messaging.destination.name", context.getExchange())
					.and("messaging.rabbitmq.destination.routing_key", context.getRoutingKey());

into out-of-the-box convention.
That one is not done yet, so keeping it opened until respective contribution.
Thanks