Feature: Persistent Storage of State

[Microno95]

Ideally, there is a persistent storage of the application state that can be revisited without having to download and upload the state.

This can be broken down into two parts:

1. Persistent state within the browser: resilience to refreshing of the page, returning to it later, etc. Uses JS LocalStorage to commit and retrieve the application state. Limited to a single shader project per browser.
2. Persistent server-side state: Uses user authentication to create db entrie server-side and retrieves application state from there.
3. [Extension] User workspaces enabling a user to work on multiple shader projects at once.