Added support for AspNetCore 7 rate limiting

[mburumaxwell]

Add support for Rate Limiting available from AspNetCore 7.0.

Caveats:

• The repo/libraries support both net6 and net7 using #if NET7_0_OR_GREATER which can potentially be a problem for maintenance.
• There is no means to validate the policy actually exists without the prescence of an interface/class similar to IAuthorizationPolicyProvider or ICorsPolicyProvider. The RateLimitingMiddleware uses RateLimiterOptions.PolicyMap but it is internal. Hopefully something will be available in AspNetCore 8 to allow validation. A TODO exists in the validation just tracking and as a reminder.
• Not possible to use default similar to AuthorizationPolicy and CorsPolicy because the EnableRateLimitingAttribute requires a policyName. Default policy would have to be configured in the serivces setup:
  services.AddRateLimiter(options => { /* conf stuff here */ });

Fixes: #1776

[Tratcher]

• There is no means to validate the policy actually exists without the prescence of an interface/class similar to IAuthorizationPolicyProvider or ICorsPolicyProvider. The RateLimitingMiddleware uses RateLimiterOptions.PolicyMap but it is internal. Hopefully something will be available in AspNetCore 8 to allow validation. A TODO exists in the validation just tracking and as a reminder.

Is there an issue tracking that in AspNetCore?

[Tratcher]

Very nice

[MihaZupan]

Thanks!

[Tratcher]

@mburumaxwell I pushed some fixes to your branch so we can get this into the upcoming preview release. Thanks for helping out.

[mburumaxwell]

@mburumaxwell I pushed some fixes to your branch so we can get this into the upcoming preview release. Thanks for helping out.

Okay. Looking forward. Should the same workflow be used for output caching? (Also introduced in .NET7)