Implement data syncing between Redux state, IndexedDB, and server

[apmwebdev]

There are several pieces of data that should be persisted in the browser. The reasons for this are varied, but include:

1. Increasing performance: It's faster to access a cached value locally while fetching data from the server in the background.
2. Enabling guest user functionality: Guest users can't persist data on the server, so there are some features that require them to write to a local storage of some sort instead.
3. Persisting state across reloads and different sessions: For auth in particular, it's important to be able to maintain state across page reloads. While this is technically accomplished via cookie, it's helpful to have the user's name locally so that it can be displayed immediately when the page is reloaded.
4. Allowing "offline mode": This is potentially a more advanced use case, but there theoretically isn't anything stopping the app from working in an offline mode if enough data is cached locally. There are lots of kinks to iron out with this, however, such as how to reconcile local state and server state.

Things to persist locally

1. ✅ Guesses and attempts
2. Puzzle data
3. ✅ Search panel searches
4. Default hint profiles
5. User hint profiles
6. Hint profile/panel state
7. User settings

Related Issues

• Add guest user functionality #4
• Add hint panel CRUD functionality #22
• Add user hint profile CRUD functionality #25
• Add default hint profile "update" functionality (i.e., saving preferences) #26
• Add user puzzle attempt delete functionality #28
• Limit the number of valid-but-incorrect guesses per attempt that the app saves #50
• Code smell: API and state logic seem overly complicated #53
• Persist guesses locally for caching and guest user access #56
• [BUG] Guest users can't switch hint profiles #57
• Add UUID sync functionality #83
• Cache puzzle data locally? #85