fix(frontend): Fix login/logout actions; update credentials cache on state change

[Pwuts]

• Resolves Credentials aren't refreshed after switching to a different user account #10008

Changes 🏗️

• Update useSupabase hook to propagate auth state changes
• Refresh CredentialsProvider whenever the user login state changes
• Add logOut callback to useSupabase hook that handles (client-side) logout
  • Remove server-side logout action: the Supabase reference implementation does it client-side, and doing both causes a race condition

Refactorings to aid implementation of the above:

• Move @/hooks/useSupabase -> @/lib/supabase/useSupabase

Other improvements:

• Clean up login server action based on reference implementation
• Make BackendAPI.isAuthenticated() more efficient and faster
• Remove unused ProfileDropdown component
• Improve logic and debug logging in tests/pages/login.page.ts
• Improve playwright test output logging

Checklist 📋

For code changes:

• I have clearly listed my changes in the PR description

• I have made a test plan

• I have tested my changes according to the test plan:

  • Log out from account (A)
  • Log in to other account (B)
  • Open builder, add a block for which account B has (multiple) credentials
  • Credentials for account B are shown
  • Credentials for account A are not shown

  Note: do not reload the page while going through these steps

[netlify]

✅ Deploy Preview for auto-gpt-docs-dev canceled.

Name	Link
🔨 Latest commit	ee44746
🔍 Latest deploy log	https://app.netlify.com/projects/auto-gpt-docs-dev/deploys/6840c8773148ee00083ec111

[netlify]

✅ Deploy Preview for auto-gpt-docs ready!

Name	Link
🔨 Latest commit	ee44746
🔍 Latest deploy log	https://app.netlify.com/projects/auto-gpt-docs/deploys/6840c8773148ee00083ec10f
😎 Deploy Preview	https://deploy-preview-10017--auto-gpt-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[deepsource-io]

Here's the code health analysis summary for commits 6629052..ee44746. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success	❗ 40 occurences introduced 🎯 46 occurences resolved	View Check ↗
Python	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[AutoGPT-Agent]

The PR template is not properly filled out - missing the checklist items and clear description of changes. However, the code changes themselves are minor, focused on frontend auth handling, and the title follows the conventional commit format with proper scope. The changes appear to be strictly related to credential handling during logout which keeps it within scope.

[AutoGPT-Agent]

While the PR shows clear code changes that make sense, the PR template is not properly filled out. The checklist sections are completely missing (not even marked as N/A) and the test plan is very minimal, only showing failed lint checks. Additionally, while the PR title follows the conventional commit format with scope, the description could be more detailed about the need for these changes. However, since you mentioned to not be overly pedantic and we're working on getting the template used at all, these issues aren't severe enough to warrant a complete rejection.

[AutoGPT-Agent]

The PR has issues with incomplete checklist. While the PR title follows conventional commit format and the description clearly explains the intent of the changes (fixing credential caching on login state changes), the author has not properly completed the checklist section. The test plan shows that the linting and type checking tests failed, but there's no indication that the actual functionality was tested. According to the rules, the checklist must be filled out completely, and partially checked off checklists are not accepted.

[AutoGPT-Agent]

The PR mostly follows the required format and rules. The title correctly uses 'fix(frontend)' format. The description references issue #10008 and clearly explains the changes. The checklist is incomplete as the author hasn't confirmed testing according to their test plan - they've created a plan but haven't marked it as completed. This is a requirement according to the rules where checklists must be filled out completely. No backend/data/*.py files are changed and no new frontend routes are added, so those specific rules don't apply.

[AutoGPT-Agent]

Thanks for your PR to fix the credentials cache on login state change! Before we can merge this, please complete the checklist by confirming that you've tested your changes according to the test plan you outlined. The test plan looks comprehensive, but we need confirmation that you've actually run through the steps and verified the expected behavior (credentials for account B showing, credentials for account A not showing).

[AutoGPT-Agent]

Thank you for your PR addressing the credentials cache update on login state change! The changes look good technically - you're updating the useSupabase hook to respond to auth state changes and refreshing credentials when the logged-in user changes.

A couple of things to address before this is ready to merge:

1. It appears you haven't completed testing your changes according to the test plan you outlined. Please follow through with the testing steps you've described (logging out from account A, logging into account B, etc.) and check off that item in the checklist once you've verified everything works as expected.

2. Your test plan is very clear, but I'd like to confirm - have you observed that without this fix, credentials from account A would incorrectly persist when switching to account B without a page reload?

The code changes themselves look good - subscribing to auth state changes and properly cleaning up the subscription is the right approach here. The dependency array for the useEffect in credentials-provider.tsx has been appropriately updated to include the user as well.

[Pwuts]

still flaky |:(

[github-actions]

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

[github-actions]

Conflicts have been resolved! 🎉 A maintainer will review the pull request shortly.