test: Refactor snapshot testing

[rschristian]

What kind of change does this PR introduce?

Testing refactor

Did you add tests for your changes?

Yes

Summary

The existing snapshot tests were quite time consuming to update, as they weren't making use of Jest's snapshots. Every time a file hash changed or output deviated beyond the +/- 5% bound, the contributor would need to manually update. When a few hashes or output sizes changed, this was a slow and annoying process.

This PR switches over to using actual snapshots, though there is a downside: Jest has no "Snapshot sorta matches" functionality, so if there's any deviation at all in a file size, we need to update. I don't see this as too much of an issue though, as it's so quick to update (simply append -u to the test command, and Jest itself informs you of this). Also, it's a nice canary for changes that shouldn't have changed output sizes at all -- in the past, anything within +/- 5% would be hidden.

This will greatly reduce the time I spend updating tests after I've determined a change should be made to the stored images.

Does this PR introduce a breaking change?

N/A

[changeset-bot]

⚠️ No Changeset found

Latest commit: effd025

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[rschristian]

Test failure is due to differing paths in comments in SSR bundle. Need to think on that, don't really want to do too much fiddling with bundles to normalize, but we might need to.