Support reentrant pop orderly

[xdkxlk]

Is Your Feature Request Related to a Problem? Please Describe It

For pop orderly, when we pop some messages from a message queue, this queue will be locked during invisible time. During this time period, the message will not be visible to other consumers.
However, in the event of an error such as a network disruption, the broker may mistakenly assume that some messages have been sent to the client when in fact they have not been received. In such cases, the messages can only be re-consumed after the invisible time has elapsed. This will lead to message delay.

Describe the Solution You'd Like

We can introduce a new parameter attemptId in PopMessageRequestHeader.
When the broker detects that the attemptId is same as the previous attemptId, this request can obtain the lock, even during the invisible time.
If a client encounters any network exceptions, it should retry to pop message with the same attemptId.

Describe Alternatives You've Considered

Additional Context

• Support reentrant pop orderly for broker #6691
• Support reentrant notification orderly for broker #6761
• Support reentrant orderly consumption for proxy #6754