CLPR: Proper ClprEndpointClient Behavior

This issue is a placeholder for the work related to implementing the correct `ClprEncpointClient` behavior. This is expected to evolve over time, but at minimum this needs to do the following:
1. Partition and distribute the ledgers to connect to as clients across the participating nodes so that no remote ledgers are connected to by multiple clients at the same time, and the nodes that perform the connecting vary over time so that the protocol makes progress through honest nodes across all ledgers.
1. This is to reduce the amount of redundant transactions and to ensure that no ledger is starved from making progress by malicious nodes.

Start with issue #23252, which is the only entry point named and describes the intended ClprEndpointClient behavior. Define how ledger connections are partitioned across participating nodes, how connecting nodes vary over time, and how completion will demonstrate reduced duplicate connections and progress across all ledgers.

Written by the indexing model from the issue text.