feat: Allow advanced routing patterns with RabbitMQ plugin

[luislhl]

Acceptance Criteria

The RabbitMQ plugin should allow usage of advanced routing patterns in RabbitMQ.

For this, it should accept 2 new arguments: the exchange name and routing key, and validate whether either an exchange or a queue is provided, not both.

Previously it only supported sending to a single queue, which prevented developers from using it to send messages to Exchanges, which are needed for some more advanced routing strategies (see https://www.rabbitmq.com/tutorials/amqp-concepts#exchanges)

Security Checklist

• Make sure you do not include new dependencies in the project unless strictly necessary and do not include dev-dependencies as production ones. More dependencies increase the possibility of one of them being hijacked and affecting us.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.28%. Comparing base (33a03ed) to head (62c99f1).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #531      +/-   ##
==========================================
+ Coverage   88.05%   90.28%   +2.22%     
==========================================
  Files          54       54              
  Lines        2345     2358      +13     
  Branches      439      446       +7     
==========================================
+ Hits         2065     2129      +64     
+ Misses        256      213      -43     
+ Partials       24       16       -8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.