[Bug] Fix pop orderly commit offset when NO_MATCHED_MESSAGE

[drpmma]

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

Not related

RocketMQ version

5.2.0

JDK Version

No response

Describe the Bug

When pop orderly returns NO_MATCHED_MESSAGE, it will invoke popBufferMergeService.addCkMock which is an async offset commit behavior leading to potential repeat offset.

Steps to Reproduce

Pop orderly with NO_MATCHED_MESSAGE, then pop message successfully.

What Did You Expect to See?

Repeat offset or repeat message consumption

What Did You See Instead?

No repeat

Additional Context

No response