[Enhancement] Optimize the message queue write selector used by proxy

[redlsz]

Before Creating the Enhancement Request

• I have confirmed that this should be classified as an enhancement rather than a bug/feature.

Summary

There may be certain issues with the org.apache.rocketmq.proxy.service.route.MessageQueueSelector when selecting write queue by filters.

1. The intention of #selectOneMessageQueue is traversing each candidate queue until find eligible one, but this index can be increased concurrently by multiple threads. Therefore, in one traversal, some queues may be accessed more than one time, while some others may not be accessed.

2. The #transferQueue2Addressable doesn't traverse brokerActingQueues. So if select by onlyBroker=true, the transferred result is always null.

Motivation

Make proxy MessageQueueSelector work as expected.

Describe the Solution You'd Like

1. Add new MessageQueueReadSelector to extend MessageQueueSelector, using ThreadLocalIndex as write selector index.

2. Remove unnecessary transferring between MessageQueue and AddressableMessageQueue.

Describe Alternatives You've Considered

/

Additional Context

No response