AAD B2C support notice for articles

[guardrex]

Fixes #36366

Wade, Tom ... Should I place this notice in the main doc set includes for use everywhere (and address B2C mentions everywhere), not just for Blazor?

Dan ... This deals with product support, so I definitely would like to address your feedback on it.

After the text of the notice is settled, I'll go about sprinkling this in where B2C appears.

NOTE TO SELF 🦖 ...

Just in case we go in this direction, the markdown is ...

[!INCLUDE[](~/blazor/includes/azure-active-directory-b2c-support-notice.md)]

[wadepickett]

I think it would be better to keep any details on how support continues (dates and conditions etc.) out of this note and rely on the central support details page where it is reviewed and controlled by the pertinent stakeholders.

(I am out of office Monday 11/24 to 11/25.)

[guardrex]

Sure thing ... I hear you on that. It's not necessarily as discoverable that way. For example, a dev could look at the B2C WASM article at ...

https://learn.microsoft.com/en-us/aspnet/core/blazor/security/webassembly/standalone-with-azure-active-directory-b2c?view=aspnetcore-10.0

... and either ...

• Have no idea that it's going to be mothballed, going down a rabbit hole with tech that they will lose eventually.
• Get confused by going to look for it in Azure and not finding it because their Azure account is created after the May 1st cutoff.

In the past, we've used remarks like this to make moving 🧀 with tooling and Azure features a bit clearer. This note will go away completely, probably along with many other B2C mentions, at .NET 15.

Anyway, I'm 👂 to hear how you want to handle it, and then I'll take steps from there, possibly closing this PR/issue out as a 'won't-fix' based on your decision(s) and modifying my current PR at #36367.