Remove OpenAPI analyzers in .NET 11

[Youssef1313]

See https://learn.microsoft.com/en-us/aspnet/core/breaking-changes/10/openapi-analyzers-deprecated?view=aspnetcore-10.0

These analyzers have been deprecated in .NET 10 Preview 7 (LTS release).

We are still shipping them in .NET 11 so far (STS release).

I think it might make sense to drop them in .NET 12.

Related code:

https://github.com/dotnet/sdk/blob/a49e3d7e5c5cd104e16bf63902d1059716c712ac/src/WebSdk/Web/Targets/Sdk.Server.targets#L57-L61

https://github.com/dotnet/sdk/blob/a49e3d7e5c5cd104e16bf63902d1059716c712ac/src/WebSdk/Web/Targets/Sdk.Server.props#L50-L53

https://github.com/dotnet/aspnetcore/tree/5997c34364c4405108a4cc48bed1610e25e0fa1c/src/Mvc/Mvc.Api.Analyzers

[javiercn]

@danroth27 we can drop these in 11, don't we? Deprecation only applies to runtime code. Am I wrong?

[github-actions]

Triage Summary

Area: area-minimal (OpenAPI analyzers live under the OpenAPI/minimal APIs area)
Type: Task (code removal/deprecation cleanup task, not a bug or new feature)

Potential Duplicates

• None found

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by Triage Comment Reviewer for dotnet/aspnetcore for #68087 · 14.9 AIC · ⌖ 6.3 AIC · ⊞ 8K · ◷

[danroth27]

@danroth27 we can drop these in 11, don't we? Deprecation only applies to runtime code. Am I wrong?

Anything that was obsolete in .NET 10 can be removed in .NET 11.

[Youssef1313]

I added this to RC1 milestone.