Investigate catching UI upgrade errors

[leafty]

When a new Renku release is deployed, the UI asset files are moved around (they contain hashes in their path) which causes errors in the browser.

Some examples:

• Importing a module script failed.
• Failed to fetch dynamically imported module: https://renkulab.io/assets/GroupPageContainer-RtuQaWcW.js
• Unable to preload CSS for /assets/ScrollableModal-NKeOHMAo.css

In the Error Boundary component, we already try to catch these errors so that we reload the current page which should load the latest version of the UI.

Lastly, the UI page may be blank after an upgrade because the browser tries to load the entrypoint script index.js but it has moved with the new release.