Add support for automatic inference from runtime concepts to OpenAPI annotations

[captainsafia]

We've got a few issue tracking how we want to implement automatic generation of OpenAPI details from runtime constructs but we don't have a list of the heuristics we'd like to include in whatever strategy we land with.

• Route groups should automatically produce OpenAPI tags based on the prefix used.
• The document-level OpenApiServers type should be populated from the IServerAddressesFeature.
• Automatic resolution of authentication and authorization configuration (tracked more directly via Automatically infer OpenApiSecuritySchemes from authentication configuration #39761)

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[captainsafia]

Closing this for now.

I think the right approach is to introduce these heuristics piece meal into the new built-in OpenAPI support as we roll out new framework features/refine the support.