Enable Tracing for RabbitMQ Component when we move to their v7

[eerhardt]

Once we have a build of RabbitMQ.Client with rabbitmq/rabbitmq-dotnet-client#1261, we will need to enable and document the "RabbitMQ.Client" ActivitySource for our component.

One thing to note is that we added our own ActivitySource for the connection retries we do:

https://github.com/dotnet/aspire/blob/4032b57cf197184214362a8cc6b829c3b557821c/src/Components/Aspire.RabbitMQ.Client/AspireRabbitMQExtensions.cs#L23-L24

We should think about how to rectify the 2 activity sources in the future. One possibility is that once open-telemetry/semantic-conventions#454 is completed, we might not need our own ActivitySource for tracing the connection tries.

[davidfowl]

Moving into preview milestone @eerhardt

[eerhardt]

Moving to backlog, as RabbitMQ doesn't have a stable v7 package yet. We can do this when we update for the v7 version.

[davidfowl]

Is there a new package yet?

[eerhardt]

Is there a new package yet?

https://www.nuget.org/packages/RabbitMQ.Client/

Latest version is 7.0.0-rc.9