Consider adding step for coverage check in GH

[gpsaggese]

How difficult it is to just have a GH check to see if coverage as increased or decreased

[Shaunak01]

We already run a weekly coverage check that flags if overall coverage drops by more than 1%. Adding coverage checks to every pull request feels unnecessary for two main reasons.

• A single PR typically won’t cause a meaningful shift in overall coverage. And if a PR adds untested code, it’s generally clear from the review itself
• Running full coverage (including fast, slow, and possibly superslow tests) on every PR would introduce significant compute overhead and slow down the CI pipeline

[gpsaggese]

All good points, no need to work. But let's leave it open for future reference and mark paused