Websocket refactoring and improvements

[Doru991]

In this PR, the following changes were made to the websocket implementation:
* Extracted the WS initialization procedure from the data() function to its own method initWebsocket which is called from the data function instead.

• The spellcaster connection is now fully managed by the wsConnection class.
  • wsConnection emits events when requiring the main application to complete a token exchange/handshake with od-spell-caster (when first opening the app, or when connection is temporarily lost)
  • wsConnection will forward all message-received events to the main app for decoding.
  • Once fully initialized, wsConnection is fully autonomous as long as handshake requests are properly handled. The main app binds to wsConnection once and doesn't need to keep track of web sockets opening or closing when connection is lost and restored.
• When the websocket is closed, it will attempt to reinitialize itself every 5 seconds until re-establishing connection.
• Messages received from spellcaster are now timestamped correctly.

Minor: Minutes are now padded properly (ex. 18:6 -> 18:06)

Because this is a relatively complicated architecture (compared to the rest of the frontend) I'll include the following diagram to help understand the sequence
of events:

[kickhead13]

holy FUCK this is cool. Lers get this merged

[kickhead13]

Let's try to move the websockets stuff into its own file.

[catyuzu23]

nice work

[kickhead13]

I found a weird issue on Ubuntu X11 i3WM running tauri ontop of webkit. I will be creating a github issue for this and we will investigate it.

I approve this change as is.