test: block-stm app

[cloudgray]

Description

Closes: #XXXX

Inject block-stm-enabled app into existing tests

This PR should be merged after #845 is merged

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• tackled an existing issue or discussed with a team member
• left instructions on how to review the changes
• targeted the main branch

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 62.84%. Comparing base (8f242bf) to head (b1d5909).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #879      +/-   ##
==========================================
- Coverage   64.06%   62.84%   -1.22%     
==========================================
  Files         318      318              
  Lines       22289    22217      -72     
==========================================
- Hits        14279    13963     -316     
- Misses       6572     7042     +470     
+ Partials     1438     1212     -226     

Files with missing lines	Coverage Δ
encoding/config.go	100.00% <100.00%> (ø)
x/vm/keeper/keeper.go	85.23% <100.00%> (+10.95%)	⬆️

... and 51 files with indirect coverage changes

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

[aljo242]

can we add this back?

[cloudgray]

@aljo242
I branched this PR off of PR #825, and the removal of the -race flag was a change introduced in PR #825.
We may need confirmation from @vladjdk, the author of PR #825.

@vladjdk
Was this change intentional?
As far as I know, enabling the -race option allows data race detection, but it also increases the build size as well as execution time and memory usage.