Fundamentals overview article overhaul

[guardrex]

Fixes #37558
Addresses #34356

• Focusing on Blazor and Minimal APIs throughout. Keeping references to MVC and RP where appropriate for older versions.
• Improving, usually simplifying, some examples that I feel show a lot of code and complexity to make simple points for introductory/fundamentals reading. Let's see on review if I went too far 🙈😄.
• Shedding the INCLUDES versioning, which fixes the broken links in prior release content and cuts content duplication. 🎉
• For some sections, I knock out detailed feature content in favor of allowing the subject matter articles in those areas handle the coverage. It leans some of the sections more in the direction of a general overview.
• I'm rewriting a few of the sections to make them simpler for new-to-.NET devs and new-to-programming devs. This is an early article, so I hope we can avoid relying too much on prior knowledge.
• Drop these sample apps that are bloating the repo, not linked for reader download/use, and out of date. It simplifies and reduces the cost 💸 of maintaining the article and doc set. The stable code that was supplied is easily inlined for the shorter examples.
• Let's move the Environments section UP to place it before other sections that mention execution environments.
• Let's move the general guidance on the definition of DOM, byte multiples, and support requests to the main Fundamentals overview article and out of Blazor's Fundamentals overview article. I edited the content so that it applies to the entire doc set.

---

Internal previews

File	Preview link
aspnetcore/blazor/fundamentals/index.md	Learn preview
aspnetcore/fundamentals/index.md	Learn preview
aspnetcore/fundamentals/index/snapshot/Program10.cs	Learn preview
aspnetcore/fundamentals/index/snapshot/Program11.cs	Learn preview
aspnetcore/fundamentals/index/snapshot/Program6.cs	Learn preview
aspnetcore/fundamentals/index/snapshot/Program8.cs	Learn preview
aspnetcore/fundamentals/index/snapshot/Startup3.cs	Learn preview
aspnetcore/fundamentals/static-files.md	Learn preview

Build report

[wadepickett]

@guardrex: Approved. I think it is better. Well done. Outside of this immediate PR we should have a good lively discussion on the pro-cons and "when if'"s of moving compilable code examples to non-compilable snapsots on any large scale of overhalls so we have some consistant direction with the outcome we want.

[guardrex]

I agree. Let's take it up next week while still working on this PR. We'll probably come up with some improvements to this.

[wadepickett]

I agree. Let's take it up next week while still working on this PR. We'll probably come up with some improvements to this.

This PR is fine (unless the scope for some reason increases ), but for outside of this PR's scope good to figure out more generally what other types of content fit the move to uncompiled snapshot files and what doesn't, and when at least one clean compilable working example is warrented even when using snapshots.

@tdykstra just for CC as we think about this going forward.

[wadepickett]

@guardrex: This PR is approved and can be squashed and merged.