[BUG] When you have a bad key, the message is not informative and there is an error on the page

[RobertLRead]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce

Go here, which is a valid URL with an "x" appended:
https://gosqas.org/provenance/8FFYE6suyVbCtVAWe2sP8Yx

It says it loads forever.

Then go here:

https://gosqas.org/provenance/8FFYE6suyVbCtVAWe2sP8Y

And see the difrerence.

Note it thows an error on the page (bad promise) that you can see in the debugging tools:

Expected behavior
We should give an informative message saying "This is not a valid history key", and suggesting they go to a our home page, with a link provided.

Screenshots
If applicable, add screenshots to help explain your problem.
https://gosqas.org/provenance/8FFYE6suyVbCtVAWe2sP8Y

Desktop (please complete the following information):
Chrome browser, from a Mac omputer.

[RobertLRead]

@ninalahoti can you design a simple page for this and then assign it to Ben to assign to a developer?

[bencoombs]

The device page catches that error so we could do the same on the provenance page?

[ninalahoti]

https://www.figma.com/design/nFA3vMmmL6DdoOIpBmLgIC/Brand-Guidelines?node-id=2060-504&t=zNzSw9ufnJZ9s0LI-1 Thoughts on this page design and text? @RobertLRead @vjaqua

[vjaqua]

One text edit:
In place of the word "email" just say the email [email protected]

[ninalahoti]

Made the edit! @bencoombs I believe this is ready to be assigned now

[vjaqua]

This would resolve #386 and #276