[Enhancement] Why are the conditions for lock and unlock multiplied by 2 and 3 respectively? It seems a bit strange.

Why are the conditions for lock and unlock multiplied by 2 and 3 respectively? It seems a bit strange.

这里*2 和 *3 似乎有点奇怪，不知道是不是写错了。

https://github.com/apache/rocketmq/blob/10c650c48724d052b1b5c6406b8c28cbcd86d3bf/proxy/src/main/java/org/apache/rocketmq/proxy/common/ReceiptHandleGroup.java#L123

https://github.com/apache/rocketmq/blob/10c650c48724d052b1b5c6406b8c28cbcd86d3bf/proxy/src/main/java/org/apache/rocketmq/proxy/common/ReceiptHandleGroup.java#L143

In addition, the time should be checked before acquiring the lock; otherwise, as the queue accumulates, it will become increasingly slow and unable to quickly process expired items.

另外，应该判断时间，再获取锁，否则队列堆积的时候，会越来越慢，无法把过期的快速处理掉。

Start in proxy/src/main/java/org/apache/rocketmq/proxy/common/ReceiptHandleGroup.java at the referenced lines 123 and 143. Trace the lock and unlock conditions and the time check while considering queue accumulation; done means the multiplier behavior and lock ordering are confirmed or corrected, with the resulting expired-item processing verified.

Written by the indexing model from the issue text.