[Exploration]: maintaining the same websocket connection between client side pages (even with SSR tools)

[Marvin Frachet]

Describe the bug

When navigating between pages using an SSR framework, depending on how the users want to wrap their page with Progressively's provider, the WebSocket connection can be interrupted when the page unmounts and re-created when landing on the next page.

Since most modern SSR frameworks are able to handle client-side routing effectively once the application is started in the browser, it might be a good idea to keep the socket connection instead of closing / reopening it