feat: adust block duration in set_avg_block_durarion with config

[noa-starkware]

Note

Medium Risk
Changes the on-chain reward calculation input (avg_block_duration) by clamping it to governance-configured bounds, which can alter emitted block rewards and payout amounts. Also bumps starkware_utils to a new git revision, introducing upstream behavior changes.

Overview
Block-reward calculations now enforce configured block-time bounds. RewardSupplier::set_avg_block_duration clamps the computed average block duration to block_duration_config min/max before persisting, replacing the previous TODO.

Tests are extended with a new helper (advance_epoch_global_custom_time) and a new case that drives block times below/above the configured range to assert both the clamped avg_block_duration and resulting rewards. The PR also updates the starkware_utils / starkware_utils_testing dependency revision.

^{Written by Cursor Bugbot for commit 7ef4637. This will update automatically on new commits. Configure here.}

---

This change is 

[remollemo]

@remollemo reviewed 6 files and all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on NirLevi-starkware).

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.83%. Comparing base (137d12b) to head (7ef4637).
⚠️ Report is 7 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #68      +/-   ##
==========================================
+ Coverage   95.81%   95.83%   +0.01%     
==========================================
  Files          42       42              
  Lines       10342    10385      +43     
==========================================
+ Hits         9909     9952      +43     
  Misses        433      433              

☔ 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.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

[cursor]

Clamp with uninitialized config zeroes out block rewards

High Severity

For upgraded contracts (where the constructor doesn't run), block_duration_config remains at its default storage value of {0, 0} since the EIC to initialize it is only a TODO. The new .clamp(0, 0) call forces calculated_block_duration to 0 on every epoch, which then sets avg_block_duration to 0, making total_rewards permanently zero. Before this change, the raw calculated value was used directly, allowing the system to self-correct. Now there's no recovery without an external set_block_duration_config call or EIC deployment.

Additional Locations (1)

• src/reward_supplier/reward_supplier.cairo#L94-L96