HTTP/3 Client migration behind LB

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Is your feature request related to a problem? Please describe the problem.

Does ASP.NET Core support QUIC Client migration when using HTTP/3, and there are multiple servers behind a load balancer? Assuming the load balancer using source-destination addresses for balancing?

The issue described here: https://www.rfc-editor.org/rfc/rfc9000.html#name-considerations-for-simple-l

### Describe the solution you'd like

I am curious if this is feasible at all.

### Additional context

_No response_

Start with the linked RFC 9000 section and review ASP.NET Core's HTTP/3 and QUIC client support. Determine whether client connection migration works when multiple servers sit behind a source-destination load balancer, and document whether the behavior is supported or what constraints apply.

Written by the indexing model from the issue text.