Allow passing a "RestClient.Builder" as constructor argument for "RestClient*TokenResponseClient"

Expected Behavior

Instantiating a RestClient*TokenResponseClient (e.g. RestClientTokenExchangeTokenResponseClient) should allow passing a RestClient.Builder as constructor argument, in order to use an instrumented HTTP client without having to duplicate code.
The current implementation uses RestClient.builder(), thus missing the instrumentation.

Ideally, I could write something like:

var tokenExchangeTokenResponseClient = new RestClientTokenExchangeTokenResponseClient(restClientBuilder);

Current Behavior

Using an instrumented HTTP client (managed by Spring Boot application) in RestClient*TokenResponseClient requires duplicating code, as in:

var restClient = restClientBuilder
    // this code comes from AbstractRestClientOAuth2AccessTokenResponseClient
    .messageConverters(messageConverters -> {
        messageConverters.clear();
        messageConverters.add(new FormHttpMessageConverter());
        messageConverters.add(new OAuth2AccessTokenResponseHttpMessageConverter());
    })
    .defaultStatusHandler(new OAuth2ErrorResponseErrorHandler())
    .build();

var tokenExchangeTokenResponseClient = new RestClientTokenExchangeTokenResponseClient();
tokenExchangeTokenResponseClient.setRestClient(restClient);

Context

Related issue for the reactive clients due to the use of WebClient.Builder(): https://github.com/spring-projects/spring-security/issues/14946.

Start by locating AbstractRestClientOAuth2AccessTokenResponseClient and the RestClient*TokenResponseClient classes, then inspect their constructors and current RestClient.builder() usage. Check the related reactive-client issue for context and existing tests. Done means the clients can receive a RestClient.Builder while retaining the required converters and error handler configuration.