patch history nice-to-haves

[michaelpalumbo]

• need a strategy for page reloads: should history still be loaded from indexedDB or loaded from database (if latter, is there a way to ensure that that is not considered a fork? otherwise we'd have new forks on each reload and page visit.
• prevent saving the patch history to the db more tahn once between patch edits (i.e. we don't want to fill the db with duplicates of a patch history) (right now i can spam the 'save history' button and it make a bunch of the same entries with new IDs
• update the lobby page to list stats about the patch history currently in use in each room (authors, modules, number of edits, number of forks)
• Once the patch history database is done, make it so that when the demo synth is loaded, it includes a patch history (in reality, it would be a patch history that gets loaded and includes the file.fpsynth in its automerge doc