feat: Improve consensus test ergonomics with snapshot testing

[Jiloc]

Description

This PR is about simplifying the process of writing and updating our consensus tests.

the current drill: write a test, run it, see it fail, extract the data and then manually recreate the ExpectedResult struct from the terminal back into your code. It's easy to mess up.

This change introduces snapshot testing using a crate called insta.

Long story short: with this, we don't have to write the ExpectedResult by hand!

So, how does it work

Instead of stuffing the ExpectedResult into our test files, insta saves it automatically into a separate .snap file (or inline, I have an example). These new files live in a snapshots/ directory and we check them into Git. They become the "source of truth" for what the output should be.

Pros:

• Writing the tests should be easier. You just write the test setup and let insta generate the correct output for you.
• Our test files look cleaner. They're all about the logic, not giant blocks of data.
• Easy Diffs for Reviews: When a change breaks consensus, the git diff on the .snap file will show exactly what changed in the output. Reviewing consensus-breaking changes should be easier.
• Updating the fixtures on consensus-breaking releases can be automated

---

How do I use this?

Writing a new test:

1. Set up your ConsensusTestVector like before, but just... don't add an expected_result.
2. Run the test logic: let result = ConsensusTest::new(...).run();
3. Add this magic line at the end: insta::assert_ron_snapshot!(result);
4. Run cargo insta review to create the snapshot for you:

   cargo insta review

5. Run the test
6. Just commit the new .snap file along with your code.

Updating a test after you broke something (on purpose!):

1. Run cargo test. It'll fail, and insta will print a beautiful diff showing you exactly what's different.
2. If the new output is correct and expected, just run cargo insta review again.
3. insta will automatically update the snapshot file for you.
4. Commit your code and the updated snapshot. Your PR will now have a clear "before and after" of the consensus change.

Applicable issues

• fixes #

Additional info (benefits, drawbacks, caveats)

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

[jferrant]

Oh interesting. I am surprised this didn't break the test. Thought it would complain about insufficient stx.

[Jiloc]

Yeah I found out that the boot_nakamoto function used internally already gives funds to the private key passed

stacks-core/stackslib/src/chainstate/nakamoto/coordinator/tests.rs

Line 180 in b6fc3ff

peer_config.initial_balances = vec![(addr.to_account_principal(), 1_000_000_000_000_000_000)];