Str 106 csm test util

[purusang]

Description

Consolidates repeated testing logic to a single function.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature/Enhancement (non-breaking change which adds functionality or enhances an existing one)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactor
• New or updated tests
• Dependency Update

Notes to Reviewers

Please suggest on handling test_l1_reorg(). Do we not apply writes for this particular case?

Checklist

• I have performed a self-review of my code.
• I have commented my code where necessary.
• I have updated the documentation if needed.
• My changes do not introduce new warnings.
• I have added tests that prove my changes are effective or that my feature works.
• New and existing tests pass with my changes.

Related Issues

STR-106

[codecov]

Codecov Report

Attention: Patch coverage is 98.16514% with 4 lines in your changes missing coverage. Please review.

Project coverage is 58.53%. Comparing base (0ea3c38) to head (8be3149).
Report is 20 commits behind head on main.

Files with missing lines	Patch %	Lines
...rates/consensus-logic/src/csm/client_transition.rs	98.16%	4 Missing ⚠️

@@            Coverage Diff             @@
##             main     #514      +/-   ##
==========================================
+ Coverage   56.45%   58.53%   +2.07%     
==========================================
  Files         273      277       +4     
  Lines       29079    29328     +249     
==========================================
+ Hits        16416    17166     +750     
+ Misses      12663    12162     -501     

Files with missing lines	Coverage Δ
...rates/consensus-logic/src/csm/client_transition.rs	64.40% <98.16%> (+2.38%)	⬆️

... and 71 files with indirect coverage changes

[delbonis]

Minor cleanups.