Add Blazor with .NET on Web Workers article

[guardrex]

Fixes #36370

Ilona ...

• Sample app is up for review at Add Blazor WASM .NET on Web Workers sample app blazor-samples#635.
• We've been using -o|--output for sample creation. -n|--name was in the raw content and used for the React article. I'm moving both to -o. Let me know if you think that's a poor choice. I know -o creates the folder and names the app. I thought -n only names the app. Truthfully tho, I only really ever used -o.

---

Internal previews

📄 File	🔗 Preview link
aspnetcore/blazor/blazor-with-dotnet-on-web-workers.md	aspnetcore/blazor/blazor-with-dotnet-on-web-workers
aspnetcore/client-side/dotnet-on-webworkers.md	aspnetcore/client-side/dotnet-on-webworkers
aspnetcore/toc.yml	aspnetcore/toc

[Copilot]

Pull Request Overview

This PR adds a new Blazor-specific article about using .NET on Web Workers and updates the existing React-focused article to clarify its scope. The changes enable better documentation organization by separating Blazor and React implementations while maintaining cross-references between them.

Key changes:

• New article explaining Web Workers integration in Blazor WebAssembly apps with QR code generation example
• Updated React article description and sample references to clarify React-specific focus
• Changed CLI sample creation from -n|--name to -o|--output parameter for consistency

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
aspnetcore/blazor/blazor-with-dotnet-on-web-workers.md	New comprehensive article demonstrating Web Workers in Blazor WebAssembly with code examples for QR generation
aspnetcore/client-side/dotnet-on-webworkers.md	Updated to clarify React-specific focus, fixed sample app name, changed CLI parameter from -n to -o
aspnetcore/toc.yml	Added TOC entry for new Blazor Web Workers article under WebAssembly section

[ilonatommy]

Looks good

[ilonatommy]

• We've been using -o|--output for sample creation. -n|--name was in the raw content and used for the React article. I'm moving both to -o. Let me know if you think that's a poor choice. I know -o creates the folder and names the app. I thought -n only names the app. Truthfully tho, I only really ever used -o.

I don't have any preference, I didn't even notice that. You're right that -n only names the app, does not embed the project in a folder.
-o creates a folder of the chosen name. -n names the app because it says "If no name is specified, the name of the current directory is used."

[guardrex]

@danroth27 ... I haven't heard back if you want to look at this one. I'll hold it until later today (Monday) to give you a chance to look. If you end up having post-merge feedback, I'll place a patch PR.