#585 #1229 #1598 #1915 Rate limiting global configuration

[MiladRv]

Closes #585 #1229 #1915

• Support global configuration of load balancer and rate limiting options etc. #585
• Global rate limiting for all, multiple routes instead of every route #1229
• Rate limiter not working #1598
• Apply rate limiting globally  #1915

Proposed Changes

This PR implements global rate limiting per #1229.

• Adds new GlobalRateLimitOptions in Configuration
• Adds new FileGlobalConfiguration in File

Successor

• #2138 Introduce ASP.NET rate limiting #2188
  Next, this pull request will be merged.

Predecessors (feature history)

• #1590 Use correct interval for request counting #1592
• #372 use period timespan to decide when client can make requests again #404
• Rate limit #37

[coveralls]

coverage: 90.173% (+0.8%) from 89.393%
when pulling 55a703b on MiladRv:feature/add-global-rate-limit
into 265f9b4 on ThreeMammals:develop.

[raman-m]

Hello, Milad!
Thank you for this great PR! I'll be reviewing the code shortly...
However, since Coveralls has reported a decrease in coverage by -0.7%, we need to write unit tests—ideally covering all new code. Unit tests are a crucial part of our development process ❕ Read points 4 and 5.

[raman-m]

Yellow card penalty! 🟨

Thank once again for submitting this PR However, after the code review, I consider it a draft.
The primary concern is the lack both unit and acceptance tests ❗
While your intention to add documentation is appreciated, please note that documentation should be written upon the completion of the code (at the end of development).

Several minor but important issues need to be addressed as listed below 👇

1. I recommend starting with the file models design.
2. Please be aware that the linked #1229 issue requires grouping routes by a key. Prioritize this type of grouping initially, and upon completion, proceed with the Patterns concept.
3. Presenting your ideas using patterns and method grouping is also necessary. However, I do not support your idea of including the "Methods" feature, as it mixes concerns.

P.S. I will provide my vision of the model's design at a later stage.
P.P.S. I anticipate several rounds of code review. However, this feat has high priority, and I will support you through multiple pair-programming sessions.
P.P.P.S. Other members from the Ocelot development team could review this PR and provide separate code feedback 😉
Life, indeed, not easy 😛