Ignore runtime_limit test

[bogdan-stacks]

This PR adds an ignore flag for block_limit_runtime_test.

This test can be ignored as it is specific to execution cost limits in the interpreter.

fix: stx-labs/clarity-wasm#692

[CLAassistant]

All committers have signed the CLA.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 30.29%. Comparing base (e38da9a) to head (486f236).
⚠️ Report is 3 commits behind head on feat/clarity-wasm-develop.

❌ Your project status has failed because the head coverage (30.29%) is below the target coverage (80.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files

@@                      Coverage Diff                      @@
##           feat/clarity-wasm-develop    #6624      +/-   ##
=============================================================
- Coverage                      31.10%   30.29%   -0.81%     
=============================================================
  Files                            572      572              
  Lines                         358768   358768              
=============================================================
- Hits                          111597   108692    -2905     
- Misses                        247171   250076    +2905     

Files with missing lines	Coverage Δ
stacks-node/src/tests/integrations.rs	0.00% <ø> (ø)

... and 91 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 4d8e162...486f236. 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.