Add documentation for synchronous access to asynchronous operations

[Copilot]

This PR addresses the common scenario where developers need to call asynchronous methods but cannot use await throughout their call stack. This situation often occurs in legacy codebases or when integrating async methods into synchronous APIs.

The new section "Synchronous access to asynchronous operations" provides practical guidance on:

• GetAwaiter().GetResult() - The preferred approach when blocking is unavoidable, as it preserves original exceptions without wrapping them in AggregateException
• Task.Run wrapper pattern - For complex scenarios where isolating async work on a thread pool thread can help avoid deadlocks
• Wait() and Result - Documented as discouraged approaches due to poor exception handling and higher deadlock risk

The documentation includes:

• Clear warnings about deadlock risks and performance impacts
• Code examples for each approach
• Links to Stephen Toub's authoritative blog post on sync wrappers
• Appropriate emphasis that async/await throughout the call stack remains the preferred solution

This enhancement follows the guidance from @stephentoub and @BillWagner to provide practical options while keeping "dangerous" patterns appropriately cautioned with clear warnings about their risks.

Fixes #37040.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

---

Internal previews

📄 File	🔗 Preview link
docs/csharp/asynchronous-programming/async-scenarios.md	docs/csharp/asynchronous-programming/async-scenarios

[BillWagner]

This is a good start, I have a few comments.

[BillWagner]

@copilot address the review comments.

[BillWagner]

This is ready for final review.