[Bug] Fix metrics and transactional not shutdown cause broker coredump

[lizhimins]

Before Creating the Bug Report

• I found a bug, not just asking a question, which should be created in GitHub Discussions.

• I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.

• I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Runtime platform environment

MacOS 13.5.1 / Linux 4.19

RocketMQ version

latest develop branch (5.1.3)

JDK Version

JDK11

Describe the Bug

When the broker shutdown gracefully, if the metrics timing task happens to be executed at this time, and the delay message module has been closed normally, the broker will accesses illegal direct memory, causing broker coredump.

当 Broker 正常关闭时（优雅下线），metrics 和 transactional 两个服务没有正常关闭。
假如此时 metrics 定时任务正好执行，但是定时消息模块已经正常关闭了，此时 broker 在下线时访问了非法内存，造成 coredump

Steps to Reproduce

No

What Did You Expect to See?

Broker shutdown normally

What Did You See Instead?

Broker coredump

Additional Context

No response