chore: shorten signature offence suspension

[dandanlen]

Based on observations in perseverance, I think it makes sense to shorten this.

When have a lot of false positives (which can happen due to network conditions), we risk banning 'good' nodes. This tens to happen particularly when there is a large volume of simultaneous signature requests.

150 blocks is a long time to wait to recover, and in the meantime, more requests accumulate, making the situation worse.

We still need to suspend misbehaving nodes though, so removing the suspension altogether is not an option.

5 blocks is a decent compromise: it allows for up to 5 retries before the banned nodes come back into play, meaning we strike a balance between flushing out bad nodes, and recovering from network degradation.

In future we might want to consider some form of escalation whereby we hand out longer suspensions for repeat offenders.

[codecov]

Codecov Report

Merging #4170 (4548e36) into main (ed0baff) will increase coverage by 0%.
Report is 2 commits behind head on main.
The diff coverage is n/a.

@@          Coverage Diff          @@
##            main   #4170   +/-   ##
=====================================
  Coverage     72%     72%           
=====================================
  Files        379     379           
  Lines      61544   61548    +4     
  Branches   61544   61548    +4     
=====================================
+ Hits       44104   44124   +20     
+ Misses     15140   15125   -15     
+ Partials    2300    2299    -1     

see 9 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more