[Bug] Fix wrong option value for namesrvAddr parsing in timer benchmark examples

[majialoong]

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

All

RocketMQ version

develop

JDK Version

All

Describe the Bug

In TimerProducer and TimerConsumer, the namesrvAddr is incorrectly parsed by reading option 't' (topic) instead of 'n' (namesrvAddr).

Steps to Reproduce

Using -n to specify namesrvAddr, but it resolves to Topic.

What Did You Expect to See?

The namesrvAddr should be parsed from the -n option value.

What Did You See Instead?

The namesrvAddr was incorrectly set to the -t option value.

Additional Context

No response