feat(chat): enable Duo Chat for SM instances
Description
Disable Duo Chat for non SaaS accounts (!1161 - merged) limited the Duo Chat's availability to SaaS accounts only. This is because back in the day we didn't support Duo Chat on the self-managed instances.
However, it's about to be changed with Supporting GitLab Duo (chat) for SM and Dedicated (&11251 - closed) scheduled to be introduced in %16.8 - Duo Chat is supposed to be available for the self-managed instances of GitLab of versions 16.8+
This MR doesn't completely revert Disable Duo Chat for non SaaS accounts (!1161 - merged) to keep the ability of detecting a SaaS account, but instead, it switches to the more generic mechanism and renders Duo Chat if there's at least one account connected to the Workflow extension.
Related Issues
Resolves #1199 (closed)
How has this been tested?
The changes in this MR have been extensively tested in the following environments/scenarios:
-
In the desktop VSCode with:
- just local GDK account connected
- SaaS account connected
- both local GDK and SaaS accounts connected
-
In the local instance of Web IDE with:
- SaaS account connected
- the local GDK account connected
Screenshots (if appropriate):
Types of changes
-
Bug fix (non-breaking change which fixes an issue) -
New feature (non-breaking change which adds functionality) -
Breaking change (fix or feature that would cause existing functionality to change) -
Documentation -
Chore (Related to CI or Packaging to platforms) -
Test gap
Related to #1199 (closed)