Ensure resource limit APIs can be used by existing implementations

[JunTaoLuo]

This is part of epic: https://github.com/dotnet/aspnetcore/issues/27464.

This issue tracks the work to ensure existing rate limits implemented can adopt the new abstractions.

Candidates to consider:

• ACR
• ATS
• OneAccess
• R9

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[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.

[adityamandaleeka]

I'm not sure this is actionable anymore. @BrennanConroy I'm closing this, but reopen if you think it's needed.