Feature request: Global catch-all for unhandled error that could crash the app and cause users to lose data

### Similar requests

- [X] I have searched and found no existing similar requests

### How are you using Legend?

Legend Studio, Legend Query

### What problems are you trying to solve?

For editors like Query and Studio, we need a global strategy to deal with unhandled exception/error that could potentially break the app. We don't want something like https://github.com/finos/legend-studio/issues/2015 to happen since it can cause loss of valuable work

### Describe the solution you would like to see implemented

- [ ] Consider setting error-boundary https://www.npmjs.com/package/react-error-boundary - allow setting this at app level, but we should really output as much data of the current user as possible, e.g. in Query: the current query, in Studio: the current entities (we can download them to a file for people)
- [ ] We should expose critical stores like `QueryEditorStore` or `EditorStore` in `window` object (via something like `ApplicationStore.debugService` (note that we need to test if the methods of these object gets obfuscated by bundler's uglifier or not)

### Describe alternatives you have considered

_No response_

### Documentation, Design, Adoption, Migration Strategy

_No response_

### Contribution

- [ ] I would like to work on this feature

Start by reading the app-level error handling entry points and the mentioned QueryEditorStore, EditorStore, and ApplicationStore.debugService. Compare how Query and Studio currently hold the current query or entities, then define a concrete recovery strategy and acceptance criteria for preserving that data after an unhandled error.

Written by the indexing model from the issue text.