Disable Roomote Control on logout

[cte]

After logging out we're not able to fetch the roomote control settings and we were short-circuiting the disconnect logic in the case that the setting fetch failed.

---

Important

Disable remote control on logout by updating BridgeOrchestrator and ClineProvider logic and adding tests.

• Behavior:
  • BridgeOrchestrator.isEnabled() now returns false if user is null or remoteControlEnabled is false.
  • ClineProvider.remoteControlEnabled() disconnects BridgeOrchestrator if enabled is false or userInfo is null.
  • extension.ts calls provider.remoteControlEnabled(false) on logout.
• Tests:
  • Added extension.spec.ts to test authStateChangedHandler calls BridgeOrchestrator.disconnect() on logout.
• Misc:
  • Updated logging messages in extension.ts for clarity.

^{This description was created by for 9ef637c. You can customize this summary. It will automatically update as commits are pushed.}

[roomote]

Thank you for your contribution! I've reviewed the changes and found that they correctly implement the feature to disable remote control on logout. The code is clear with good comments. I have a few suggestions for improvement, particularly around type safety.

[roomote]

Is this intentional? The connectOrDisconnect() method now requires a non-null userInfo parameter, but it's being called from ClineProvider.remoteControlEnabled() where userInfo could be null. This type mismatch could lead to runtime errors.

Consider either:

1. Making userInfo nullable here: userInfo: CloudUserInfo | null
2. Or ensuring all callers check for null before calling this method

[cte]

There are no type mismatches; the build would fail otherwise.