[release/8.0] fix ReceiveFrom with dual mode socket

[github-actions]

Backport of #92086 to release/8.0

Fixes #92006

/cc @karelz @wfurt

Customer Impact

Regression against .NET 7.0

When UDP user uses IPv4 address (on machine with IPv6 enabled as well - which is typical scenario), they may get wrong peer address from Socket.ReceiveFrom (the main API for receiving data for UDP). As a result, they may start sending UDP packets to the wrong endpoint - potentially leading to privacy problems.
There is a workaround to pass the address with correct AddressFamily, but that requires the developer to anticipate the problem.

The regression was introduced by PR #89841 (UDP perf improvements).

Testing

Targeted tests are added in the PR
Verified on E2E original repro from #92006 (using managed QUIC implementation side project)

Risk

Medium. UDP is used much less than TCP (also partially due to its suboptimal performance prior to .NET 8.0).

[ghost]

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

Issue Details

---

Backport of #92086 to release/8.0

/cc @karelz @wfurt

Customer Impact

Testing

Risk

IMPORTANT: If this backport is for a servicing release, please verify that:

• The PR target branch is release/X.0-staging, not release/X.0.

• If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

Author:	github-actions[bot]
Assignees:	-
Labels:	area-System.Net.Sockets
Milestone:	-

[rzikm]

LGTM, I also verified the change on the original repro and it fixes the issue.

[karelz]

I approve - it is a regression and the fix is not that complicated. Given the privacy concerns, I would take it.

@artl93 ready for your approval

[artl93]

M2 Approved.

[carlossanlop]

The tvos-arm64 legs might be stuck.

[wfurt]

The tvos-arm64 legs might be stuck.

it is finished now, all check are green.