[Bug] [cli] Pulsar-client cli doesn't support timeout values given in apache pulsar reference website

### Search before asking

- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.

### Read release policy

- [X] I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.

### Version

OS: Linux, macOS
Java: 17
Pulsar Client and Broker: 3.2.2

### Minimal reproduce step

- Update the `conf/client.conf` file with `lookupTimeoutMs`, `operationTimeoutMs` and other timeout values described [here](https://pulsar.apache.org/reference/#/3.2.x/client/client-configuration-client)
- Run `pulsar-perf` or `pulsar-client` and observe the logs.
- We get this info log from `org.apache.pulsar.client.impl.ConsumerStatsRecorderImpl` where the timeout values doesn't change with the configuration.

> `"operationTimeoutMs":30000,"lookupTimeoutMs":30000`

### What did you expect to see?

The timeout values getting picked up from the `conf/client.conf`.

### What did you see instead?

The timeout values are always default values.

### Anything else?

This works fine with Java client. The pulsar-cli tools have this issue.

### Are you willing to submit a PR?

- [X] I'm willing to submit a PR!

Start with conf/client.conf and the pulsar-perf or pulsar-client entry points, then trace how client timeout settings reach ConsumerStatsRecorderImpl. Compare this path with the Java client behavior described in the issue. Done means the configured timeout values are picked up by the Pulsar CLI tools instead of the defaults appearing in the logs.

Written by the indexing model from the issue text.