Tracking issue for self-adaptive rate limit in self protection

[CabinfeverB]

Development Task

Summary:
Refer to #4373.
We have implemented gRPC rate-limit and HTTP rate-limit by manually setting the rate-limiting parameters.
But it's hard to set a speed limit. Because the carrying capacity of different clusters is different, and the carrying capacity of different interfaces in different loads is also different.

So we should provide a mechanism to set rate limit adaptively.

Here are some references for applying the tcp BBR algorithm to system traffic limiting scenarios.
https://github.com/alibaba/Sentinel/wiki/%E7%B3%BB%E7%BB%9F%E8%87%AA%E9%80%82%E5%BA%94%E9%99%90%E6%B5%81
https://github.com/go-kratos/aegis/blob/main/ratelimit/bbr/bbr.go

Goal

1. Adaptive rate limiting for a single API: For the hot path API, when the processing speed of an API reaches the bottleneck, speed-limiting measures are taken to prevent the OOM/CPU overload caused by request accumulation.
2. Adaptive service degradation. Carding API priority, when achieving the bottleneck of high priority API drop low priority API with tighter speed limit configurations to improve overall availability PD.

Tasks：

• Implement BBR algorithm for a single API

  • Sliding Time window #7230
  • pkg/ratelimit: refactor for BBR #7239
  • ratelimit: impl BBR-like algorithm #7246
  • ratelimit: apply BBR in limiter #7277
  • ratelimit: support modify BBR config by API #7291
  • rate_limit: add metrics #7343

• Adaptive service degradation

  • Which APIs to choose and classify
  • Degraded reference metrics, and metrics collection, such as CPU
  • Impl algorithm

mics

• tools: improve api bench #7345