Antiforgery integration for minimal APIs

See [Antiforgery integration for minimal APIs](https://devblogs.microsoft.com/dotnet/asp-net-core-updates-in-dotnet-8-preview-7/#antiforgery-integration-for-minimal-apis)

and [this sample](https://github.com/dotnet/AspNetCore.Docs.Samples/blob/main/fundamentals/minimal-apis/samples/MyAntiForgery/Program.cs#L16-L17)

In [this code](https://github.com/dotnet/AspNetCore.Docs.Samples/blob/main/fundamentals/minimal-apis/samples/MyAntiForgery/Program.cs#L57) I pass in the action so

```
app.MapGet("/DisableAntiforgery", () =>
{
return Results.Content(MyHtml.html("/todo"), "text/html");
});

app.MapGet("/post2", () =>
{
return Results.Content(MyHtml.html("/todo2"), "text/html");
});
```

Can use the same HTML when they pass in the action arg.

Is there a clean way to do this to pass in an arg for
```

```

Maybe that makes things too messy. Perhaps I should duplicate most of the HTML and not get the HTML from a method while passing the action.

```
public static string html2(string action, AntiforgeryTokenSet token) => $"""









""";
```
Works, but I'm not sure it's an improvement. There's no way to pass in a null token.

@sammychinedu2ky @david-acker

cc @guardrex

Comienza con los puntos de entrada referenciados de fundamentals/minimal-apis/samples/MyAntiForgery/Program.cs, especialmente con la generación de HTML alrededor de las líneas 16–17 y 57. Compara cómo se pasan el argumento action y AntiforgeryTokenSet al marcado del formulario; se considera terminado cuando el ejemplo tiene un enfoque claro y mantenible, sin una cuestión de token nulo sin resolver ni HTML duplicado innecesariamente.

Escrito por el modelo de indexación a partir del texto del issue.