[Bug] SlaveActingMaster Timer Message retry without escape logic

[AYue-94]

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

RocketMQ version

5.1.1

JDK Version

8

Describe the Bug

In slaveActingMaster mode, when master down, minId slave broker become proxy master.
When proxy master put timer message back to commitlog fail on first time, it may lost escape logic.

rocketmq/store/src/main/java/org/apache/rocketmq/store/timer/TimerMessageStore.java

Line 1064 in a7d493b

public int doPut(MessageExtBrokerInner message, boolean roll) throws Exception {

while (retryNum < 3) {
          // ...
          Thread.sleep(50);
          putMessageResult = messageStore.putMessage(message); // focus here
          LOGGER.warn("Retrying to do put timer msg retryNum:{} putRes:{} msg:{}", retryNum, putMessageResult, message);
      }
}

Steps to Reproduce

1. enable slaveActingMaster（NameServer&Broker）；
2. producer send some timer message；
3. master down；
4. minId slave become proxy master，begin to scan timer message；

What Did You Expect to See?

timer message put back to commitlog fail, it should has escape logic when retry.

What Did You See Instead?

proxy master directly write its commitlog, although it will fail because slave is readonly.

Additional Context

No response