Improve system storage and data structure

[bryanlundberg]

What does this PR do?

• Implement a backup panel and compatibility with the backup from other online timers.
• Change from localStorage to indexDB
• Improve execution time for calculating statistics
• Improve rendering resolves (React renders only the visible part of the array of solves, avoiding rendering +30k items per refresh). It was a issue for big data sets.

Related Issue(s)
#226

Screenshots or GIFs (if applicable)

Importing status:

Checklist

• Import panel
• Nexus timer compatibility
• csTimer compatibility
• TwistyTimer compatibility
• Cubedesk compatibility
• Transition from localStorage to indexDB
• Error handling corrupted files
• Translations for import modal

[bryanlundberg]

Need add - Compress images and redirect to /cubes after a successful import

[bryanlundberg]

Need optimization; restoring from a large text file, crashes the browser.

[bryanlundberg]

Requires changing from localStorage to indexedDB due to low storage capacity

[bryanlundberg]

Additional testing is required at the moment. Currently, no errors have been detected in the standard system after migrate from localStorage to indexDB. We can proceed to resume the import feature.

[bryanlundberg]

Its needed allow users to edit the cube category from /cubes since Cubedesk and CSTimer its not easy deduce the original category, and it could even be mixed. Will be the user's responsibility to make the necessary corrections.

[bryanlundberg]

The current implementation is very slow and redundant writting and reading DB. The application experiences dropdowns in FPS that almost crash the browser when updating the selected cube statistics calculations after each solve and moving between pages.

It becomes notably slow, especially when there are more than 20,000 solves. (Big amount of data)

We can try removing unnecessary data pulls from the database (each read takes 2s), instead, maintain a updated copy in memory.

[bryanlundberg]

The low performance might be related to the multiple uses of 'useTimerStatistics.ts', causing the rendering of overall statistics five times each time a solve its added.

statistics calculations are excecuted 5times each render.

[bryanlundberg]

calculations now are stored a single time with zustand state, instead multiple states everywhere.

• Statistics refresh when cubes data are changed (only 1 time).
• Optimized loops inside statistics functions

Before: 2500 - 3000 ms - 1 render

After: 23ms - 1 render

[bryanlundberg]

OK