[fix][client] add maxRetryRequestTimes in ClientConfigurationData and remove Duplicate retry logic

[walkinggo]

Motivation

The maxRetries property of AsyncHttpConnector is derived from the config of DefaultAsyncHttpClient.

@SneakyThrows
    public AsyncHttpConnector(int connectTimeoutMs, int readTimeoutMs,
                              int requestTimeoutMs,
                              int autoCertRefreshTimeSeconds, ClientConfigurationData conf,
                              boolean acceptGzipCompression) {
        Validate.notEmpty(conf.getServiceUrl(), "Service URL is not provided");
        serviceNameResolver = new PulsarServiceNameResolver();
        String serviceUrl = conf.getServiceUrl();
        serviceNameResolver.updateServiceUrl(serviceUrl);
        this.acceptGzipCompression = acceptGzipCompression;
        AsyncHttpClientConfig asyncHttpClientConfig =
                createAsyncHttpClientConfig(conf, connectTimeoutMs, readTimeoutMs, requestTimeoutMs,
                        autoCertRefreshTimeSeconds);
        httpClient = createAsyncHttpClient(asyncHttpClientConfig);
        this.requestTimeout = requestTimeoutMs > 0 ? Duration.ofMillis(requestTimeoutMs) : null;
        this.maxRetries = httpClient.getConfig().getMaxRequestRetry();
    }

This causes both DefaultAsyncHttpClient and AsyncHttpConnector to share the same retry count value. However, since both components implement their own retry logic, this configuration actually results in accumulated retries exceeding the configured limit. Given that DefaultAsyncHttpClient has a default retry count of 5, I propose disabling retries in DefaultAsyncHttpClient (setting its retry count to 0) while maintaining the default configuration, to centralize retry handling exclusively within AsyncHttpConnector.

Modifications

1. Retry Configuration Support
   Added maxRetryRequestTimes in ClientConfigurationData (default: 5) to control admin client request retry behavior. Configuration propagates to AsyncHttpConnector implementations.

2. Client API Enhancements

• Extended ClientBuilder interface with new maxRetryTimes() method
• Implemented configuration injection in ClientBuilderImpl

3. HTTP Connector Refactoring

• Modified AsyncHttpConnector to use centralized configuration instead of AsyncHttpClient's internal retry setting
• Explicitly disabled underlying library retry via confBuilder.setMaxRequestRetry(0)

4. Validation
   Added parameter verification test in ClientBuilderImplTest to validate retry time configuration constraint

Documentation

• doc
• doc-required
• doc-not-needed
• doc-complete

Matching PR in forked repository

PR in forked repository: walkinggo#9

[thetumbled]

Changes related to configuration modification need a pip.

[walkinggo]

Changes related to configuration modification need a pip.

Apologies, this PR was created in response to an existing TODO comment. I'll promptly draft a PIP document and submit it to the community mailing list.