feat(kafka): ensure allocated resources are removed on failures

[thalesmg]

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

This also introduces the following changes that were uncovered during development:

• Improved Kafka Consumer logging when the node is shutting down to reduce noise.

• We now ensure the bridge resources are removed if an exception happens during its creation to avoid leaking resources.

• We changed the emqx_resource_manager_sup restart strategy from simple_one_for_one to one_for_one.

  Using simple_one_for_one has a potential race condition issue where we read the PID of the resource manager before trying to remove a resource, and then that PID changes because it was either dead at first, or it crashed and changed, and later we use this stale PID to try to remove it from the supervisor. Under such circumstances, the restarting child might linger in the supervisor, leaking resources.

  By using the resource ID itself as a child ID (and using one_for_one restart strategy), we ensure the child is truly removed.

Summary

🤖 Generated by Copilot at 1f74d26

This pull request adds resource management and telemetry for the kafka and pulsar bridges using the emqx_resource module. It also updates the version numbers, the change logs, and the test cases for the bridge applications. The changes aim to improve the reliability and observability of the bridges.

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

Checklist for CI (.github/workflows) changes

• If changed package build workflow, pass this action (manual trigger)
• Change log has been added to changes/ dir for user-facing artifacts update

[coveralls]

Pull Request Test Coverage Report for Build 5094422552

• 52 of 59 (88.14%) changed or added relevant lines in 7 files are covered.
• 132 unchanged lines in 17 files lost coverage.
• Overall coverage decreased (-0.04%) to 81.595%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
apps/emqx_bridge/src/emqx_bridge.erl	5	6	83.33%
apps/emqx_bridge_kafka/src/emqx_bridge_kafka_impl_consumer.erl	20	23	86.96%
apps/emqx_bridge_kafka/src/emqx_bridge_kafka_impl_producer.erl	17	20	85.0%

Files with Coverage Reduction	New Missed Lines	%
apps/emqx_bridge_kafka/src/emqx_bridge_kafka_impl_consumer.erl	1	81.76%
apps/emqx_gateway_mqttsn/src/emqx_mqttsn_channel.erl	1	73.18%
apps/emqx_gateway_mqttsn/src/emqx_mqttsn_frame.erl	1	63.48%
apps/emqx_s3/src/emqx_s3_profile_conf.erl	1	93.07%
apps/emqx/src/emqx_cm.erl	1	91.6%
apps/emqx/src/emqx_limiter/src/emqx_limiter_schema.erl	1	75.44%
apps/emqx/src/emqx_mqueue.erl	1	89.86%
apps/emqx/src/emqx_quic_data_stream.erl	1	75.21%
apps/emqx_machine/src/emqx_machine_boot.erl	2	77.46%
apps/emqx/src/emqx_banned.erl	2	89.39%

Totals
Change from base Build 5080911934:	-0.04%
Covered Lines:	28626
Relevant Lines:	35083

---

💛 - Coveralls

[zmstone]

Suggested change

	kind => Kind,
	error => Error,
	exception => Kind,
	reason => Error,

[thalesmg]

I'll fix it in the next on_stop refactoring PR.

[yanzhiemq]

Enhancements

• Refactored Kafka Producer and Consumer bridges to avoid leaking resources during crashes at creation.

[yanzhiemq]

增强

• 重构了Kafka 生产者和消费者桥接，在创建过程中避免资源泄漏。