[Feature] Develop error handling framework

[davehorsfall]

Is your feature request related to a problem? Please describe.
It would be useful to establish a consistent error handling approach, so that errors/warnings are caught, and reported back to the user is a consistent way, throughout the package.

Describe the solution you'd like
Capture errors and warnings, and report to user through the the MUI Snackbar component to report errors and warnings.

Additional context
Related to #19 #40

[davehorsfall]

After the above work on the error handling framework has been added, we need to establish some test cases to easily validate and demonstrate the error handling under various conditions.

• Hard errors (errors that prevent rendering) should display in the main window
• Soft errors (errors that impact rendering or spec) should display in toast notifications
• All errors/warnings/info/debug should (optionally) display in console
• The above should be linked under a common logging system
• The API should support exposing errors externally, and be able to receive errors (from plugins) into the system

@AlexSurtees to review, and share screenshots, example links.

[AlexSurtees]

Logging system - levels of errors/warnings, a way of controlling what level of logging is reported to the console/other consumers.

Make sure we have documented examples to show error handling/warning handling.

[davehorsfall]

@davehorsfall to review UI and error messages. Especially, CORs

[AlexSurtees]

PR #95 implements these changes, apart from allowing external errors to be handled by the viewer (e.g. from plugins).

Automated tests were implemented for 404, 403, 401, and missing/invalid metadata.

404:

https://deploy-preview-95--biongff-vizarr.netlify.app/?source=https%3A%2F%2Flivingobjects.ebi.ac.uk%2Fidr%2Fzarr%2Fv0.5%2Fidr0162A%2F6001240_labels.zarr&roi=0&viewState=%7B%22target%22%3A%5B48.83394979437483%2C49.55474610130287%5D%2C%22zoom%22%3A3.123936169260733%7D

CORs:

https://deploy-preview-95--biongff-vizarr.netlify.app/?source=https%3A%2F%2Fstatic.webknossos.org%2Fmisc%2F6001240.ozx&roi=0

403/401 don't have any test images. Tested via automated tests that just return these status codes and make expectations on the error type, error code, etc. that is raised by the viewer.

Example warning can be viewed here:

https://deploy-preview-95--biongff-vizarr.netlify.app/?source=https%3A%2F%2Fs3.janelia.org%2Fahrens-lab%2Fruettenv%2FExM%2F250531_foxj1a_eGFP_NPVF_mCherry_7dpf%2Fdorsal%2F250531_foxj1a_egfp_npvf_mcherry_7dpf_dorsal.zarr&roi=0&viewState=%7B%22target%22%3A%5B1022.83%2C1822.1280000000002%5D%2C%22zoom%22%3A-2.0765210909684138%7D