Prerendering guidance organization

[guardrex]

Fixes #35904

Dan, I took a look at what we can obviously move, and I only see the Environments section that pertained to a server-side implementation of a normally client-side-only service. That makes a lot of sense to move because it's one of the ways devs can deal with prerendering that's listed in the Prerendering article (the fourth option). So ... that's moved here.

Otherwise, I think we hit a bit of a wall on the rest. The sprinkled-in coverage is tightly bound to the concepts covered for each feature/scenario. Speaking only to the prerendering aspects of these features well in advance of the feature coverage doesn't look like to me that it's going to work ... but ... perhaps we addressed your major concern from the other convo and moved most/all of what we need to move.

One more thing ...

The index is still here. I do put a little blurb there for discussion on how we could 🔪💀 the index in favor of a filtered search, but note that ...

• It only works in Google.
• It doesn't work in Bing ... or least I don't know how to make it work correctly in Bing.
• It doesn't work with our doc's built-in search ... our docs search doesn't have the ability to filter to just the Blazor node AFAIK.

I still like the index because all I need to remember is that it's here. It helped me a few times. Anywho ... I'll leave it there or cut it out 🔪 it when I hear what you'd like to do with it.

---

Internal previews

📄 File	🔗 Preview link
aspnetcore/blazor/components/prerender.md	aspnetcore/blazor/components/prerender
aspnetcore/blazor/fundamentals/environments.md	aspnetcore/blazor/fundamentals/environments