[NET] Use SetCurrentStackTrace for not thrown exceptions

[ManickaP]

Fixes #117652

[Copilot]

Pull Request Overview

This PR enhances stack trace information for not-thrown exceptions in networking libraries by using ExceptionDispatchInfo.SetCurrentStackTrace(). This helps improve debugging by providing better stack traces when exceptions are created but wrapped in Task.FromException or ValueTask.FromException rather than being directly thrown.

• Applies ExceptionDispatchInfo.SetCurrentStackTrace() to exceptions used with ValueTask.FromException and Task.FromException
• Adds necessary using System.Runtime.ExceptionServices; statements where needed
• Updates exception creation patterns to preserve stack trace information for better debugging

Reviewed Changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
WebSocketStream.cs	Wraps NotSupportedException and ObjectDisposedException instances with SetCurrentStackTrace
ManagedWebSocket.cs	Applies SetCurrentStackTrace to WebSocketException and OperationCanceledException
Socket.Tasks.cs	Wraps NotSupportedException with SetCurrentStackTrace
SocketsHttpHandler.cs	Applies SetCurrentStackTrace to various HTTP-related exceptions
Http3RequestStream.cs	Wraps ObjectDisposedException instances with SetCurrentStackTrace
Http2Stream.cs	Applies SetCurrentStackTrace to NotSupportedException, HttpRequestException, and ObjectDisposedException
Http2Connection.cs	Wraps ObjectDisposedException and IOException with SetCurrentStackTrace
ContentLengthWriteStream.cs	Applies SetCurrentStackTrace to HttpRequestException instances
HttpContent.cs	Wraps HttpRequestException instances with SetCurrentStackTrace

[dotnet-policy-service]

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

[rzikm]

LGTM

[CarnaViire]

Thanks!