Fix selecting HTTP client builders for Eureka Client

[OlgaMaciaszek]

Currently, if there's a builder bean for HTTP client (RestClient.Builder, WebClient.Builder, etc.) created by the user, it's used for creating the client used for communication with Eureka. The problem with this approach is that it's not readily visible for the users and we may end up using builder beans with a setup that was not intended by the users to be used for communicating with Eureka (for example, a @LoadBalanced RestClient.Builder). Consider switching to an approach where if there's a builder identified by the user for this specific purpose (for example, by a specific supplier function or interface), it's used, if not, we create our own and use available configurers/customisers on it to make sure the Boot-provided capabilities, such as metrics support are there.

See:

• 2024RC1: LoadBalancer with Eureka Discovery Client throws: Error creating bean with name 'scopedTarget.eurekaClient': Requested bean is currently in creation #4380 (comment)
• Missing observability support in RestTemplateTransportClientFactory  #4255

[hyunw9]

Hello, I’m interested in this issue. If no one has taken it yet, may I work on it?

[spencergibb]

Hold off for now. We need to do some design work as a team.