Explore how we prevent end-users tests failing between minor releases

## Summary
Spike to explore how we prevent end-users tests failing between minor releases

## 💬 Description
Currently, some end-users tests are failing between minor releases as we make small changes, even if those are small changes or changes behind the scenes that don't change the look of the component. This spike should consider how we prevent this 100% of the time, to ensure teams can upgrade minor versions without it breaking their tests at all. Exploration can include how other libraries do this and if it'd differ between testing libraries. The outcome should be either a system to prevent it, or issues to implement the findings if they're large features.

## 💰 Use value
Improve the experience of teams upgrading the components.

## Additional info
Is this potentially where we utilise snapshot testing more strictly?

This is an exploratory spike rather than a scoped code change, and the issue names no files, tests, or entry points. Compare how other libraries and testing libraries prevent end-user tests from breaking between minor releases, including whether stricter snapshot testing helps. Done means documenting a prevention system or filing follow-up issues for larger findings.

Written by the indexing model from the issue text.