feat(circuit breaker): add sliding window for request result tracking

[liuzengh]

No description provided.

[codecov]

Codecov Report

Attention: Patch coverage is 95.16129% with 3 lines in your changes missing coverage. Please review.

Project coverage is 99.72%. Comparing base (66256ef) to head (f383d5d).

Files with missing lines	Patch %	Lines
circuit_breaker.go	95.16%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##               v3    #1020      +/-   ##
==========================================
- Coverage   99.82%   99.72%   -0.10%     
==========================================
  Files          18       18              
  Lines        3919     3961      +42     
==========================================
+ Hits         3912     3950      +38     
- Misses          5        9       +4     
  Partials        2        2              

Flag	Coverage Δ
unittests	99.72% <95.16%> (-0.10%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[liuzengh]

https://failsafe-go.dev/circuit-breaker/#time-based-resolution

Time based circuit breakers use a sliding window to aggregate execution results. As time progresses and newer results are recorded, older results are discarded. In order to maintain space and time efficiency, results are grouped into 10 time slices, each representing 1/10th of the configured failure threshold period. When a time slice is no longer within the thresholding period, its results are discarded. This allows the circuit breaker to operate based on recent results without needing to track the time of each individual execution.