feat: add compat test with hard-coded expected cost

[hstove]

This is a PR that cherry-picks the integration test from #6448 directly on top of develop. This allows us to verify that the resulting execution cost of the type of contract we're fixing in 6448 is consistent (ie not consensus breaking) with the change in that PR.

[hstove]

Closing since #6448 is merged

[codecov]

Codecov Report

❌ Patch coverage is 0% with 71 lines in your changes missing coverage. Please review.
✅ Project coverage is 80.25%. Comparing base (863429f) to head (daab158).
⚠️ Report is 75 commits behind head on develop.

Files with missing lines	Patch %	Lines
stacks-node/src/tests/signer/v0.rs	0.00%	64 Missing ⚠️
stackslib/src/chainstate/stacks/miner.rs	0.00%	7 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##           develop    #6487       +/-   ##
============================================
+ Coverage    65.71%   80.25%   +14.53%     
============================================
  Files          558      558               
  Lines       343277   343348       +71     
============================================
+ Hits        225575   275537    +49962     
+ Misses      117702    67811    -49891     

Files with missing lines	Coverage Δ
stackslib/src/chainstate/stacks/miner.rs	80.36% <0.00%> (-0.59%)	⬇️
stacks-node/src/tests/signer/v0.rs	1.45% <0.00%> (-0.73%)	⬇️

... and 348 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 863429f...daab158. Read the comment docs.

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

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.