Ideas for Models that run too long

[OAGr]

I often have an issue where I accidentally edit a model so that it takes 60+ seconds to load, and the tab crashes. This could either be because the Squiggle code took too long to run, or the React components took too long.

Some ideas that would help:

1. Run Squiggle in Web Worker / Remotely (this would be a big feature, probably better to do later)
2. We could check how long a Squiggle model has run at some frequency, within the Squiggle code. If it goes over MAXIMUM_RUNTIME, we just cancel it and return an error. This setting would be held in the backend.
3. Have a timeout for the React Rendering. Try to kill the react rendering if it takes too long.
4. Have a special "debug mode" where the model is not run. This could be triggered by:
   a. We save to the local storage the fact that the run did not complete. When the user refreshes the page, they see an option to have autorun turn off (or we just automatically turn it off).
   b. On the "Unsaved Draft" page, we either don't "Run" the new code immediately, or we provide some option for this.
   c. On that note, maybe it would be simple/good to just turn autorun to off whenever something seems off. We'd just need some way to alert this to the user.
   d. We have some option, when opening a model, to open it up without being immediately run.
5. In the view box, when there are over 100 array elements, split them up into clusters of 100, before opening.