Bump FastEndpoints and FastEndpoints.Security

[dependabot]

Updated FastEndpoints from 8.1.0 to 8.2.0.

Release notes

Sourced from FastEndpoints's releases.

8.2

---

⚠️ Goal Sponsorship Level Not Yet Met ⚠️

Please join the discussion here and help out if you can.

---

New 🎉

New 'FastEndpoints.OpenApi' package based on 'Microsoft.AspNetCore.OpenApi'

Starting with v8.2, the FastEndpoints ecosystem has switched from NSwag/Newtonsoft based Swagger/OpenAPI document generation to the more modern and Native AOT friendly Microsoft.AspNetCore.OpenApi based document generation library. Integration is provided via a new FastEndpoints.OpenApi package which corrects a few issues with the MS package as well as doing a lot of post-processing on the document model to bring feature parity with the FastEndpoints.Swagger package.

There's no immediate need for you to switch to the new package if your projects are heavily invested in NSwag based generation. Especially if you're not yet on .NET10. The new package only supports .NET10+ projects. See EOL notice below for more info.

Streaming command handlers for the command bus

The in-process command bus can now execute commands that return IAsyncEnumerable<T> streams by implementing IStreamCommand<TResult> and IStreamCommandHandler<TCommand, TResult>.

Streaming commands use the same ExecuteAsync() extension method as regular commands, support their own middleware pipeline via IStreamCommandMiddleware<TCommand, TResult>, and can be used with closed or generic command handler registrations.

x402 Payment support for endpoints

Endpoints can now require x402 payments by calling RequirePayment(...) inside Configure().

Global x402 defaults are configured with builder.AddX402() and app.UseX402(...), and the middleware only runs for endpoints that opt in. The initial release supports the exact scheme with a single accepted payment option per endpoint and uses the safer default flow of verifying first, executing the handler, and settling only after a successful response.

New 'FastEndpoints.Mcp' and 'FastEndpoints.A2A' agent integration packages

Two new beta packages are now available for exposing your existing FE endpoints to AI agent runtimes without having to build separate agent-specific controllers or handlers.

FastEndpoints.Mcp exposes opt-in endpoints as Model Context Protocol (MCP) tools over HTTP using the official MCP ASP.NET Core transport.

FastEndpoints.A2A exposes opt-in endpoints as A2A skills with an agent card and JSON-RPC SendMessage dispatcher.

Both addons execute the normal FastEndpoints pipeline in-process, including binding, validation, pre/post processors and response serialization. Nothing is exposed by default. Endpoints must explicitly opt in via this.McpTool(...), [McpTool], this.A2ASkill(...), or [A2ASkill], and each package has separate agent-facing visibility filters so REST authorization and agent visibility can be configured independently.

bld.Services
   .AddFastEndpoints()
   .AddMcp()
 ... (truncated)

Commits viewable in [compare view](https://github.com/FastEndpoints/FastEndpoints/compare/v8.1...v8.2).
</details>

Updated [FastEndpoints.Security](https://github.com/FastEndpoints/FastEndpoints) from 8.1.0 to 8.2.0.

<details>
<summary>Release notes</summary>

_Sourced from [FastEndpoints.Security's releases](https://github.com/FastEndpoints/FastEndpoints/releases)._

## 8.2

---

## ⚠️ Goal Sponsorship Level Not Yet Met ⚠️

Please [join the discussion here](https://github.com/FastEndpoints/FastEndpoints/issues/1042) and help out if you can.

---

[//]: # (<details><summary>title text</summary></details>)

## New 🎉

<details><summary>New 'FastEndpoints.OpenApi' package based on 'Microsoft.AspNetCore.OpenApi'</summary>

Starting with `v8.2`, the FastEndpoints ecosystem has switched from `NSwag/Newtonsoft` based Swagger/OpenAPI document generation to the more modern and Native AOT friendly `Microsoft.AspNetCore.OpenApi` based document generation library. Integration is provided via a new `FastEndpoints.OpenApi` package which corrects a few issues with the MS package as well as doing a lot of post-processing on the document model to bring feature parity with the `FastEndpoints.Swagger` package.

There's no immediate need for you to switch to the new package if your projects are heavily invested in `NSwag` based generation. Especially if you're not yet on .NET10. The new package only supports .NET10+ projects. See EOL notice below for more info.

</details>

<details><summary>Streaming command handlers for the command bus</summary>

The in-process command bus can now execute commands that return `IAsyncEnumerable<T>` streams by implementing `IStreamCommand<TResult>` and `IStreamCommandHandler<TCommand, TResult>`.

Streaming commands use the same `ExecuteAsync()` extension method as regular commands, support their own middleware pipeline via `IStreamCommandMiddleware<TCommand, TResult>`, and can be used with closed or generic command handler registrations.

</details>

<details><summary>x402 Payment support for endpoints</summary>

Endpoints can now require x402 payments by calling `RequirePayment(...)` inside `Configure()`.

Global x402 defaults are configured with `builder.AddX402()` and `app.UseX402(...)`, and the middleware only runs for endpoints that opt in. The initial release supports the `exact` scheme with a single accepted payment option per endpoint and uses the safer default flow of verifying first, executing the handler, and settling only after a successful response.

</details>

<details><summary>New 'FastEndpoints.Mcp' and 'FastEndpoints.A2A' agent integration packages</summary>

Two new beta packages are now available for exposing your existing FE endpoints to AI agent runtimes without having to build separate agent-specific controllers or handlers.

`FastEndpoints.Mcp` exposes opt-in endpoints as Model Context Protocol (MCP) tools over HTTP using the official MCP ASP.NET Core transport.

`FastEndpoints.A2A` exposes opt-in endpoints as A2A skills with an agent card and JSON-RPC `SendMessage` dispatcher.

Both addons execute the normal FastEndpoints pipeline in-process, including binding, validation, pre/post processors and response serialization. Nothing is exposed by default. Endpoints must explicitly opt in via `this.McpTool(...)`, `[McpTool]`, `this.A2ASkill(...)`, or `[A2ASkill]`, and each package has separate agent-facing visibility filters so REST authorization and agent visibility can be configured independently.

```csharp
bld.Services
   .AddFastEndpoints()
   .AddMcp()
 ... (truncated)

Commits viewable in [compare view](https://github.com/FastEndpoints/FastEndpoints/compare/v8.1...v8.2).
</details>