Fixing Load Balancing shuffle

[mrm9084]

Description

More load balancing fixes:

• If the customer provides more than one endpoint manually, we shuffle them before using them the first time.
• findActiveClients use to do a lot of unneeded work to recreate the active clients list every time it was called, now load balancing only creates it when we finish a loop through the client list. We also make sure when load balancing is disabled we always reload the list as we want to use the clients in priority order.

Added some tests

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• [] CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

[nroutray]

Why not just use:

if ( (activeClients.size() == 0 && configStore.isLoadBalancingEnabled()) || !configStore.isLoadBalancingEnabled()) {

  activeClients = getAvailableClients();

}

[mrm9084]

I think when I started to write it I thought there would be other paths through, but just ended up with this. I'll clean it up.