fix(client): read events will be blocked when switching to a new segment

[wenfengwang]

What problem does this PR solve?

Issue Number: NO

Problem Summary

In now version, it will be sucked to get events from segments that maximum offset less than the target offset, which was caused by the client updating route info mechanism: it maintains the last segment's endOffset as MAXIMUM_INT64, so exceeded offset doesn't trigger route info updating, only each periodical(30s) task will update route info and then consuming back to normal.

What is changed and how does it work?

Add force flag to force update route info when client meets Overflow error.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)

it can be seen the blocking time reduced to 1-2s from 10-30s

• No code

[codecov]

Codecov Report

Merging #235 (cda684a) into main (2eddcb6) will decrease coverage by 0.00%.
The diff coverage is 64.28%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #235      +/-   ##
==========================================
- Coverage   64.38%   64.37%   -0.01%     
==========================================
  Files         115      115              
  Lines       11269    11275       +6     
==========================================
+ Hits         7255     7258       +3     
- Misses       3462     3464       +2     
- Partials      552      553       +1     

Impacted Files	Coverage Δ
internal/controller/eventbus/eventlog/eventlog.go	68.09% <0.00%> (ø)
internal/controller/eventbus/block/block.go	56.09% <70.00%> (-0.32%)	⬇️
internal/controller/eventbus/controller.go	21.42% <100.00%> (ø)
internal/timer/timingwheel/timingwheel.go	87.01% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update af0805a...cda684a. Read the comment docs.

[ifplusor]

LGTM