Fix potential auto restart failure due to blocksync always true

[yzang2019]

Describe your changes and provide context

Problem identified:

• In autoRestartIfBehind we use the blockSync as a flag to determine if already lag behind to avoid additional restart signals.
• At the same time, the restart has a "cool down" period -- meaning, restart signals during cool down period are silently ignored.
• Now, if a node restarts during cool down period, the signal gets ignored and the blockSync flag will remain indefinitely true effectively disabling the self-remediation process

Fix:

• Do not set blocksync mode in auto restart handler

Testing performed to validate your change

Added unit test

[github-actions]

The latest Buf updates on your PR. Results from workflow Buf / buf (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	✅ passed	✅ passed	✅ passed	Feb 13, 2026, 7:55 PM

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 48.35%. Comparing base (7407960) to head (3aad0c6).

❗ There is a different number of reports uploaded between BASE (7407960) and HEAD (3aad0c6). Click for more details.

HEAD has 1 upload less than BASE

Flag	BASE (7407960)	HEAD (3aad0c6)
sei-chain	1	0

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #2892       +/-   ##
===========================================
- Coverage   57.15%   48.35%    -8.81%     
===========================================
  Files        2091      671     -1420     
  Lines      171524    50615   -120909     
===========================================
- Hits        98033    24474    -73559     
+ Misses      64751    24000    -40751     
+ Partials     8740     2141     -6599     

Flag	Coverage Δ
sei-chain	?
sei-cosmos	48.16% <ø> (+<0.01%)	⬆️
sei-db	68.72% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1543 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.