feat: add RabbitMQ bridge

[kjellwinblad]

Fixes https://emqx.atlassian.net/browse/EMQX-9087

Summary

🤖 Generated by Copilot at 3c0677b

This pull request adds a new feature to EMQX that allows it to communicate with RabbitMQ brokers using the bridge mechanism. It introduces a new application emqx_bridge_rabbitmq that implements the logic and configuration for the RabbitMQ bridge type. It also updates the existing modules and files to support the new feature, such as emqx_ee_bridge, emqx_resource, mix.exs, and rebar.config.erl. It provides documentation, internationalization, and common test cases for the RabbitMQ bridge feature. It also adds a docker-compose service for RabbitMQ to facilitate testing.

PR Checklist

Please convert it to a draft if any of the following conditions are not met. Reviewers may skip over until all the items are checked:

• Added tests for the changes
• Changed lines covered in coverage report
• Change log has been added to changes/{ce,ee}/(feat|perf|fix)-<PR-id>.en.md files
• For internal contributor: there is a jira ticket to track this change
• If there should be document changes, a PR to emqx-docs.git is sent, or a jira ticket is created to follow up
• Schema changes are backward compatible

[kjellwinblad]

Setting the PR to draft as I have not made the change log entry yet.

[kjellwinblad]

Thanks for very good comments. I have addressed most in a new commit and have added questions about the remaining ones.

[kjellwinblad]

Rebased and force pushed to remove merge conflicts with master.

[coveralls]

Pull Request Test Coverage Report for Build 4916612514

• 100 of 124 (80.65%) changed or added relevant lines in 4 files are covered.
• 41 unchanged lines in 15 files lost coverage.
• Overall coverage decreased (-0.05%) to 81.59%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
apps/emqx_bridge_rabbitmq/src/emqx_bridge_rabbitmq.erl	13	16	81.25%
apps/emqx_bridge_rabbitmq/src/emqx_bridge_rabbitmq_connector.erl	83	104	79.81%

Files with Coverage Reduction	New Missed Lines	%
apps/emqx_authn/src/enhanced_authn/emqx_enhanced_authn_scram_mnesia.erl	1	85.29%
apps/emqx_gateway_mqttsn/src/emqx_mqttsn_frame.erl	1	64.61%
apps/emqx/src/emqx_broker.erl	1	87.64%
apps/emqx/src/emqx_flapping.erl	1	87.27%
apps/emqx/src/emqx_logger.erl	1	80.49%
apps/emqx/src/emqx_router_helper.erl	1	86.27%
apps/emqx/src/emqx_schema.erl	1	87.5%
apps/emqx/src/emqx_banned.erl	2	89.39%
apps/emqx/src/emqx_cm.erl	2	91.44%
apps/emqx_resource/src/emqx_resource_buffer_worker.erl	3	94.89%

Totals
Change from base Build 4915258169:	-0.05%
Covered Lines:	26209
Relevant Lines:	32123

---

💛 - Coveralls

[thalesmg]

Since this is always called, perhaps we could add this to end_per_testcase?

[kjellwinblad]

In two test cases (t_make_delete_bridge and t_make_delete_bridge_non_existing_server) it is not called last (as these test cases checks that the delete had the desired effect) and I think there is some advantage to have it directly in the test cases as it makes it more explicit what the test case is doing. I have no strong feelings about this so I can make the change, if you insist that it should be in end_per_testcase.

[thalesmg]

Yes, it's fine for those two that explicitly test that behavior.

But we always want to clear all bridges during test teardown to avoid flakiness, so I think it's a good practice to do that even if there are no bridges left to delete.

[thalesmg]

Yes, it's fine for those two that explicitly test that behavior.

But we always want to clear all bridges during test teardown to avoid flakiness, so I think it's a good practice to do that even if there are no bridges left to delete.