Antiforgery doc updates

[brunolins16]

Closes #26350
Part of dotnet/aspnetcore#42586

Internal Preview URL

EDIT by @Rick-Anderson Internal Preview URL JavaScript H2 where the changes start

[brunolins16]

@Rick-Anderson I add the content with :::moniker range=">= aspnetcore-7.0" but the Preview page seems to not be working correctly because it is showing the content for 6.0 as well or maybe I did something wrong.

[Rick-Anderson]

@Rick-Anderson I add the content with :::moniker range=">= aspnetcore-7.0" but the Preview page seems to not be working correctly because it is showing the content for 6.0 as well or maybe I did something wrong.

I'll fix it after @blowdart approves the change.

[Rick-Anderson]

@guardrex are we getting all these warnings by adding 7.0 to be available in production?

[guardrex]

It all started AFAICT when they activated the "7.0" in the document version selector. Before that ... merely having moniker ranges with it ... was ok. It was also ok no matter where the 7.0 content appeared (i.e., placed at the bottom of the topic).

[Rick-Anderson]

@brunolins16 I had to do a couple commits trying to fix the build warnings so be sure to pull.

[blowdart]

Note that @pranavkm has left us now, but hi Pranav!

I'm concerned about the writing of a cookie accessible by javascript here, the cookie should flow with requests anyway, and not need to be accessible in script.

[brunolins16]

@Rick-Anderson do you want to do any additional updates?

[Rick-Anderson]

@Rick-Anderson do you want to do any additional updates?

It's good to S&M (squash and merge).