Introduce persistent state to prevent errors when reloading the application

[sidecutter]

When the client window is refreshed (i.e. via keyboard), the app forgets both the connected tactile displays and the websocket connection to the server instance. At the same time the view/route of the app stay the same, leaving the user in a broken jamming view.

Ideally, both connections should be remembered and automatically reinitiated when necessary.