Connection Pool Abstraction

[nibanks]

Describe the feature you'd like supported

In MsQuic a single QUIC connection is fixed to a single partition (generally thread and cpu). Sometimes applications want to scale traffic with a single remote peer higher than what a single CPU can handle. We should be able to easily expose a "connection pool" abstraction that can be used like a single connection, but scales across multiple CPUs.

Proposed solution

It can likely be a completely inline, header-only interface that is mostly a thin wrapper for creating multiple connections up front and then picking the ones that spread the load evenly.

Additional context

No response