[Bug] Timing message metric will be inaccurate due to incorrect deletion behavior

[GenerousMan]

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

Ubuntu

RocketMQ version

5.2.0

JDK Version

No response

Describe the Bug

When a timing message is deleted, it is implemented by sending a delete message. Since the timerlog of the timing message is actually an index, it cannot be verified in real time whether the deletion is valid, so -1 will be directly set to the metric when received.
This will lead to a problem: if the deletion behavior is invalid, the -1 operation will not be compensated, and may even cause the metric to become a negative number - which is unacceptable.

Steps to Reproduce

according to the description of the bug.

What Did You Expect to See?

the abnormal -1 should be compensated.

What Did You See Instead?

-1 will always be there.

Additional Context

No response

[3424672656]

I am interested in this problem, please assign it to me