Storage performance, offline, local first

[dohsimpson]

Current storage backed by json file prevents offline usage, also makes multi user update difficult without constant synchronization. Furthermore, await for async update calls make ui feel unresponsive, and it creates situations where clicking the complete button multiple times would register multiple completions, this wouldn't have happened, even though we can disable the completion button as a workaround, better fix is to update local data and return right away, instead of waiting for network call to finish.

And another reason is persisting json file is not scalable, the performance is going to be slower and slower over time. Preferrably, we should opt to a local first reactive data store backed by a real db.

[AsocPro]

I'm just going to throw it out there that I would love SQLite from an operation perspective. Its easy to backup/restore since its just one file and keeps the app self contained into one container with a data volume mount. That being said another database isn't a deal breaker just a personal preference for ease of use.