Set up HttpClient for ClientWebSocket.ConnectAsync

[greenEkatherine]

Fixes #72476

Detecting if we get HttpClient as a parameter in ConnectAsync -- in that case another SendAsync method should be called to provide correct options.

Most part of PR is adding HttpClient/HttpMessageInvoker into all existing tests.

[ghost]

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Fixes #72301

Detecting if we get HttpClient as a parameter in ConnectAsync -- in that case another SendAsync method should be called to provide correct options.

Most part of PR is adding HttpClient/HttpMessageInvoker into all existing tests.

Author:	greenEkatherine
Assignees:	-
Labels:	area-System.Net.Http
Milestone:	-

[ghost]

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Fixes #72301

Detecting if we get HttpClient as a parameter in ConnectAsync -- in that case another SendAsync method should be called to provide correct options.

Most part of PR is adding HttpClient/HttpMessageInvoker into all existing tests.

Author:	greenEkatherine
Assignees:	greenEkatherine
Labels:	area-System.Net
Milestone:	-

[greenEkatherine]

/azp run runtime-libraries-coreclr outerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[greenEkatherine]

/azp run runtime-libraries-coreclr outerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[MihaZupan]

There's a lot of duplication of ConnectAsync and GetConnectedWebSocket in tests.

Can they be implemented as helper methods on ClientWebSocketTestBase instead, with the only thing for tests to implement being

protected virtual HttpMessageInvoker? GetInvoker();

?

[greenEkatherine]

/azp run runtime-libraries-coreclr outerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[greenEkatherine]

Failures in the outerloop builds are unrelated