Refactor StatefulAuthProvider for static initialization and improved session management

[pastuxso]

This refactor centralizes session management, reduces duplication, and improves maintainability across the extension.

• Centralized session change notifications using a new SessionChangeHandler implemented with RxJS and a singleton pattern.
• Refactored StatefulAuthProvider to follow a singleton pattern, simplifying its lifecycle and reducing dependencies.
• Added functionality to retrieve sessions from secrets storage, avoiding potential infinite loops when checking sessions inside a session change listener.
• Removed Kernel and RunmeUriHandler dependencies from StatefulAuthProvider for better modularity.
• Introduced a new GraphQL client instantiator to encapsulate implementation details like authentication token configuration.
• Ensured Webview refreshes correctly on login/logout events.

[pastuxso]

Hi @sourishkrout,

I had to rollback the reactive approach in cloud.ts (d2040b1). Unfortunately, the subscription isn't being triggered, so the panel fails to refresh its content as intended.

I've recorded a video demonstrating the steps to test the desired functionality. Your expertise would be greatly appreciated to resolve this issue. Let me know if you need any further details!

Thanks! 🙌

login-logout.mp4

[sourishkrout]

@pastuxso When I open the Runme side panel, I'll immediately get prompted to log in. That's not right. It should display the "Sign in or create account" button first.

[pastuxso]

Just to confirm, is it happening for Stateful or Runme ext?

[sourishkrout]

Just to confirm, is it happening for Stateful or Runme ext?

I've only tested Runme so far.

[pastuxso]

@pastuxso When I open the Runme side panel, I'll immediately get prompted to log in. That's not right. It should display the "Sign in or create account" button first.

@sourishkrout, I’ve tried to replicate it for Runme, but I couldn’t. The only way to replicate is within Stateful Extension. I wonder if a specific setting might be causing this issue. Would you mind sending me a screenshot of your panel so I can take a closer look?

[sourishkrout]

@pastuxso When I open the Runme side panel, I'll immediately get prompted to log in. That's not right. It should display the "Sign in or create account" button first.

@sourishkrout, I’ve tried to replicate it for Runme, but I couldn’t. The only way to replicate is within Stateful Extension. I wonder if a specific setting might be causing this issue. Would you mind sending me a screenshot of your panel so I can take a closer look?

I believe this below is the issue. It forces the creation of a session inside the call stack without 'true' here. That being said, I wonder if the client flag should be an object and explicit. Optional arguments are easy to overlook.

diff --git a/src/extension/panels/cloud.ts b/src/extension/panels/cloud.ts
index 4c917942..6eec159b 100644
--- a/src/extension/panels/cloud.ts
+++ b/src/extension/panels/cloud.ts
@@ -59,7 +59,7 @@ export default class CloudPanel extends TanglePanel {
 
     log.trace(`${this.identifier} webview resolving`)
 
-    const html = await this.getHydratedHtml()
+    const html = await this.getHydratedHtml(true)
     webviewView.webview.html = html
     webviewView.webview.options = {
       ...webviewOptions,

[sourishkrout]

✅ LGTM