Fix crash in publication page and add error boundaries

[philippotto]

• adds error boundaries to the individual routes (except for the tracing views since these have their own boundaries)
  • a "nice" error page will be shown to the user and the error will be logged to airbrake, too
• adds top-level error boundary for route-independent react errors
• fixes rendering error when a publication doesn't have any active datasets or annotations

URL of deployed dev instance (used for testing):

• https://___.webknossos.xyz

Steps to test:

• the publication fix is a bit tedious to set up. I don't think, it needs additional testing. It will look like this (a bit naked, but this should be only an edge case, anyway):
  
• the error boundaries can be tested by:
  • navigating to admin > users
  • 
  • clicking "help" in the navbar and "ask a question" (this error boundary is route independent)
    

Issues:

• see https://scm.slack.com/archives/C5AKLAV0B/p1671099320485249 for context

---

(Please delete unneeded items, merge only when none are left open)

• Updated (unreleased) changelog
• Ready for review

[philippotto]

review will be easier by ignoring whitespace changes

[normanrz]

code looks good. i'll do some testing now

[normanrz]

Tested -> works. I was wondering if the toast is still required? Seems a bit redundant.

[philippotto]

Tested -> works. I was wondering if the toast is still required? Seems a bit redundant.

I assume you tested it locally, right? Orthogonal to the error boundaries, there is a global window.onerror handler (mainly for errors unrelated to react). Due to a peculiarity of react, that event handler is triggered again after an error boundary was activated, but only in DEV mode. See this react issue. So, in the production build, there won't be the redundant error toast. I just tested it at https://fixpublicationpage.webknossos.xyz/users.