Flow the IMeterFactory to SocketsHttpHandler on Mobile

[MihaZupan]

I realized that what was actually happening here is that we weren't passing the IMeterFactory to the SocketsHttpHandler in our HttpClientHandler.AnyMobile.cs implementation.

You would end up with 2 separate meters:

• one using the correct factory but not instrumenting the SocketsHttpHander
• another one in SocketsHttpHandler that didn't have a factory set

The test that only listened to the metrics from one factory wouldn't see the SocketsHttpHander metrics, which is why I thought we weren't using the correct handler in #90225.

[ghost]

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

Issue Details

---

I realized that what was actually happening here is that we weren't passing the IMeterFactory to the SocketsHttpHandler in our HttpClientHandler.AnyMobile.cs implementation.

You would end up with 2 separate meters:

• one using the correct factory but not instrumenting the SocketsHttpHander
• another one in SocketsHttpHandler that didn't have a factory set

The test that only listened to the metrics from one factory wouldn't see the SocketsHttpHander metrics, which is why I thought we weren't using the correct handler in #90225.

Author:	MihaZupan
Assignees:	MihaZupan
Labels:	area-System.Net.Http
Milestone:	8.0.0

[MihaZupan]

/azp run runtime-extra-platforms

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[MihaZupan]

Not seeing the failure mentioned in #90225 (comment) on Android runs anymore, so this seems to do the trick.

[wfurt]

LGTM