[11.0 P1] Blazor startup options format

[guardrex]

Fixes #34659

Note: What's New coverage for this is already on #36449.

Ilona ... This is painful on the 👁️ to look at 😄. The versioning is more complex than usual because we had the two hosting models using different approaches for a while, and I want to keep the content duplication to a minimum. I think you only need to concentrate on the code examples to confirm correct formats. I'll inspect these articles on the live site after Preview 1 releases to confirm that the articles are rendering correctly.

WRT the build failures, I think they're all related to not having the 11.0 version moniker set up yet. I think that will happen soon.

---

Internal previews

📄 File	🔗 Preview link
aspnetcore/blazor/fundamentals/environments.md	aspnetcore/blazor/fundamentals/environments
aspnetcore/blazor/fundamentals/logging.md	aspnetcore/blazor/fundamentals/logging
aspnetcore/blazor/fundamentals/signalr.md	aspnetcore/blazor/fundamentals/signalr
aspnetcore/blazor/fundamentals/startup.md	aspnetcore/blazor/fundamentals/startup
aspnetcore/blazor/globalization-localization.md	aspnetcore/blazor/globalization-localization
aspnetcore/blazor/host-and-deploy/webassembly/index.md	aspnetcore/blazor/host-and-deploy/webassembly/index

[ilonatommy]

@guardrex, tell me if I'm reading something wrong but before I read the changes I was assuming this PR is updating the docs for net11, so that we inform about the unification of format. I cannot find any monkier that is for net11, everything is < aspnetcore-11.0. Do I read it right? If so, then what is the main goal of this PR?

[guardrex]

The code that will be shown for 11.0 is actually marked >=8.0 because this format for start options was always in place for BWAs. The pattern is this ...

:::moniker range=">= aspnetcore-8.0 < aspnetcore-11.0"

LABEL: Blazor Web App:

:::moniker-end

:::moniker range=">= aspnetcore-8.0"

Blazor Web App, Blazor Server, and/or Blazor WASM code WITH the new options format. This is preexisting coverage 
on the diff because this code was always in use for BWAs. What we're doing here is versioning it >=8.0 to cover 
BWAs and for >=11.0 for Blazor Server/WASM (note that the preceding label won't appear >=11.0).

:::moniker-end

:::moniker range=">= aspnetcore-8.0 < aspnetcore-11.0"

LABEL: Blazor Server and/or Blazor WASM depending on what's being shown. We don't need this label before 8.0
because BWAs didn't exist.

:::moniker-end

:::moniker range="< aspnetcore-11.0"

Blazor Server and/or Blazor WASM code without the new options format. This example moniker assumes that 
the code goes back to the beginning, but it might be different if the feature came in later. This is just a demo
of the general pattern that the PR is following.

:::moniker-end

... and some cases are a little different from there because in some cases the preceding pattern has to be modified for when a feature arrived after a non-8.0 version.

[ilonatommy]

All examples are valid in the given version spaces. The matrix I was using to validate it, for reference:

App Type	Direct Options, <net11	Direct Options, >=net11	Nested Options, <net11	Nested Options, >=net11
Blazor Server	V	V	X	V
Standalone Blazor WebAssembly	V	V	X	V
Blazor Web App (blazor.web.js)	V	V	V	V

[guardrex]

Thanks @ilonatommy! I'm on stand-by now for when Preview 1 lands (and we still need the 11.0 version moniker to merge all of these 11.0 P1 PRs).