Server-side behaviors during static SSR

[guardrex]

Fixes #31402

Thanks @FengRuikai! 🚀

I'm mostly going off of Javier's sentiment expressed here ...

dotnet/aspnetcore#52176 (comment)

... and I'm cleaning up the approach for how we can convey this information:

• Add the guidance to the static SSR section of the Render Modes article. Include how devs should deal with these scenarios server-side.
• Clean up and cross-link that from the <NotAuthorized> content in the Security article.
• Clean up and cross-link that from the <NotFound> content in the Routing and Layouts articles.

Also, are there any other scenarios that fall into this bucket outside of <NotFound> and <NotAuthorized> content that we should add to the list here (and cross-link from outside the article)?

... and btw ... you'll see a few other small wording changes ...

• At the start of the Static server-side rendering (static SSR) section.
• In the Static SSR components spread out across the app section.

Those updates are just things that I thought I could improve in passing. They don't pertain to the PR or the issue, but I recommend looking 👀 at those additional updates given the general complexity of the coverage.

---

Internal previews

📄 File	🔗 Preview link
aspnetcore/blazor/components/layouts.md	ASP.NET Core Blazor layouts
aspnetcore/blazor/components/render-modes.md	ASP.NET Core Blazor render modes
aspnetcore/blazor/fundamentals/routing.md	ASP.NET Core Blazor routing and navigation
aspnetcore/blazor/security/index.md	aspnetcore/blazor/security/index

[MackinnonBuck]

Some smallish suggestions - might be good to get @javiercn's input before merging

[guardrex]

No response to the ping. Let's go ahead and take reader feedback at this point. If anything is amiss, I'm sure that I'll hear about it ... readers will sharpen their BEAKS and CLAWS 🦅 for me 😨😆.