feat: add defaults and public functions in clarity-vm for better tooling

[hugocaillard]

Description

Fix: #5891

With the PR, the clarity-vm can be compiled to wasm32-unknown-unknown, as it is being using the clarinet JS SDK.

It mostly hide a few things behind compilation flags.

This PR also includes a few changes that are need for clarinet. Mostly by making public certain functions.

WIth this PR, this command passes:

cargo check -p clarity --no-default-features --target wasm32-unknown-unknown

Once this is merged, this check should be added to the CI.

Checklist

• Test coverage for new or modified code paths
• Changelog is updated
• Required documentation changes (e.g., docs/rpc/openapi.yaml and rpc-endpoints.md for v2 endpoints, event-dispatcher.md for new events)
• New clarity functions have corresponding PR in clarity-benchmarking repo
• New integration test(s) added to bitcoin-tests.yml

[hugocaillard]

I just saw #6239, which is super promising for clarinet.

The two PRs enable similar things (compile to wasm), but also, this specific one (6268) add some changes needed specifically for clarinet.
I'm happy to move it in an other PR if needed

[obycode]

🎉

[hugocaillard]

@obycode
I pushed an other commit, adding #[serde(default)] to symbolic expression developer-mode properties.
That useful when the vm with developer-mode enabled fetches data from the api (eg: clarinet mainnet execution simulation), and the api doesn't return the span.

[obycode]

👍

[hugocaillard]

Thanks @Jiloc!

[Jiloc]

lgtm!

[codecov]

Codecov Report

Attention: Patch coverage is 11.11111% with 16 lines in your changes missing coverage. Please review.

Project coverage is 64.82%. Comparing base (d185f2d) to head (117b7ac).
Report is 10 commits behind head on develop.

Files with missing lines	Patch %	Lines
clarity/src/vm/costs/mod.rs	0.00%	13 Missing ⚠️
clarity/src/vm/representations.rs	0.00%	3 Missing ⚠️

❌ Your project status has failed because the head coverage (64.82%) 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             @@
##           develop    #6268      +/-   ##
===========================================
- Coverage    67.41%   64.82%   -2.60%     
===========================================
  Files          545      545              
  Lines       347403   347411       +8     
  Branches       323      323              
===========================================
- Hits        234210   225217    -8993     
- Misses      113185   122186    +9001     
  Partials         8        8              

Files with missing lines	Coverage Δ
clarity/src/vm/analysis/type_checker/v2_05/mod.rs	87.33% <100.00%> (-0.15%)	⬇️
clarity/src/vm/docs/mod.rs	71.16% <100.00%> (+26.98%)	⬆️
clarity/src/vm/mod.rs	90.38% <ø> (-0.26%)	⬇️
clarity/src/vm/representations.rs	81.17% <0.00%> (+2.44%)	⬆️
clarity/src/vm/costs/mod.rs	78.00% <0.00%> (-0.66%)	⬇️

... and 374 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 d185f2d...117b7ac. 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.

[obycode]

👍

[Jiloc]

I tested it on my end and unfortunately cargo check -p clarity --no-default-features --target wasm32-unknown-unknown is currently now working. #6238 made into develop before this PR and removed all unnecessary default-features of the crates for supporting both wasm32 in javascript and deterministic environments.

In the comments I laid out a possible fix, which is to propagate the wasm-web feature from the clarity create to the stacks-common one and use the following command to built it:

cargo check -p clarity --no-default-features --features wasm-web --target wasm32-unknown-unknown

[Jiloc]

Great, LGTM!

[obycode]

lgtm

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