Set up Sentry to capture and output front end error messages

[AnnaKahnRaspPi]

This issue is to set up Sentry to report on common UI/front end error messages (i.e. the errors a young person would see in the output/console section of the Editor).

Why this is helpful:

1. it can help give us some basic data to inform our approach/priorities when we come to tackle front end error messaging in earnest in 2023 (after we migrate off Skulpt)
2. it might help us to assess if there is anything we want to prioritise doing in the interim to refine/stop/mask errors that

Ideally:

• expect that we would want to have a list on this issue of the errors we are capturing?
• if possible be able to distinguish if they come from standalone Editor or WebComponent
• consider how/if we are able to surface these anywhere for reporting (although expectation is this may be under a separate linked issue if it is possible)

People who could help with Sentry set up if picked up when Steve/Patrick are off:
= any of the Snr Engineers (Dan, Scott or Glen)

[create-issue-branch]

Branch issues/122-Set_up_Sentry_to_capture_and_output_front_end_error_messages created!