Add Spring RabbitMQ plugin

[liuhaolong10]

Fix RabbitMQ trace disconnection and incomplete consumer trace stack (closes #13720)

• Add a unit test to verify that the fix works.
• Explain briefly why the bug exists and how to fix it.

Bug Root Cause

The original instrumentation method in the RabbitMQ plugin is executed in a dedicated thread pool for RabbitMQ message processing, which is not the same thread where consumers execute business logic. This causes trace information loss:

• The plugin can only capture "message consumed" events but cannot track subsequent business operations (e.g., MySQL/Redis calls).
• The traceId cannot be connected between producer and consumer services.

Fix Solution

1. Implement a new instrumentation method for RabbitMQ that aligns with the business logic thread, ensuring traceId continuity between producer and consumer.
2. Modify the original RabbitMQ plugin code to avoid data collection conflicts with the new spring-rabbit plugin.

Additional Notes for New Plugin

The new spring-rabbit plugin solves the problem that the original RabbitMQ plugin cannot collect messages consumed by @RabbitListener annotation, ensuring complete trace collection for spring-rabbit based RabbitMQ consumption scenarios.

• If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #13720.
• Update the CHANGES log.