Basic snapshot testing

[stalgiag]

This PR introduces basic snapshot testing for each major route.

Notes:

• I opted to use a limited set of routes after trying a version that tested all available routes. I felt that this would be too heavy a lift for testing and maintaining.
• A number of elements are removed due to unpredictability in generation. Some of these are intentionally dynamic and some have unexpected inconsistencies between my local and CI. I have clearly marked each case in clients/tests/e2e/snapshots/util.js. Some of these may be removed after the underlying inconsistency is investigated.
• Snapshot testing can present challenges with maintenance and upkeep. I'd invite reviewers to consider whether the benefit of having an easy-to-test basic content rendering is worth the tradeoff for occasionally ballooning our pull requests due to updated snapshots. I am of the opinion that it is worth it in this limited scope but I am very open to discussing the pros + cons.

[howard-e]

In acknowledging that this is an extra layer of maintenance and developing of new features, it's also a huge plus in ensuring the accuracy of such a data heavy system. Kudos for getting this going! Looks good to me!

I've left only a small inline comment but feel free to merge when ready.

[howard-e]

A think a TODO should be included for ones like this so we can explore and remove this cleaner when necessary, explaining what the issue is.

There certainly shouldn't be a mismatch with the version dates being displayed no matter the environment.

[howard-e]

Makes sense!