Duo Workflow button displayed for namespaces and users without access

Checklist

• I'm using the latest version of the extension (see the latest version in the right column of this page)
  • Extension version: Put your extension version here
• I'm using the latest VS Code version (find the latest version here)
  • VS Code version: Put your VS Code version here
• I'm using a supported version of GitLab (see README for the supported version)
  • GitLab version: Put your GitLab version here, or say "happens on gitlab.com"

Summary

GitLab Workflow v16.9.0 displays Duo Workflow as an available option in the UI, independently of duo_workflow being enabled or not. This feature is currently Private Beta and available only for GitLab Team Members, but customers are reporting seeing it and getting an error when accessing:

Steps to reproduce

1. Create a project on a Self-Managed GitLab instance without access to Duo features
2. Install GitLab Workflow v16.9.0
3. Verify that the Duo Workflow icon shows on the left bar, and accessing it shows the error seen on the screenshot above

What is the current bug behavior?

Duo Workflow icon and input terminal shows up for customers without access to it; raises an error when accessed.

What is the expected correct behavior?

Duo Workflow should not be available for users without access.

Relevant logs and/or screenshots

Field 'duoAgenticChatAvailable' doesn't exist on type 'Project'

This confirms that the instance doesn't indeed have Duo Workflow features available on its backend.

The logs also show that the user has access to the following Duo features, which do not include Duo Workflow:

Duo available features for current user: Chat (include_file_context), Code Suggestions (repository_xray,open_tabs)

Possible fixes