Log errors from the FastAuth frontend

[DavidM-D]

Currently we get really useful error messages from clients like "HTTP response not OK". This isn't super helpful and we don't really know what's causing them. Some of the error messages make it as far as far as the recovery service where we have logging, but we have trouble working out what request came from the user in question.

We need to send these errors somewhere and have a way of associating them with a user's crash.

It's been suggested (by @MaximusHaximus) that the right way would be to attach a unique ID to all logs and server requests, displaying them in any error message shown to a user.

This is a relatively large ticket so feel free to break it up a bit.

### Tasks
- [x] Discuss which service/tool we want to use to collect errors
- [ ] https://github.com/near/fast-auth-signer/issues/19
- [ ] https://github.com/near/fast-auth-signer/issues/28