Add empty state to direct config settings for admins

What does this MR do and why?

• if you are an admin and duo is turned off, you will see:
  • duo off in the nav panel (no other icons)
  • new empty state "page"
    • Configure CTA opens the configuration settings page: either project or group depending on your current namepspace
    • Learn more CTA opens the permission docs
• If you do not have admin privileges and duo is turned off, no change
  • you will see all the nav buttons disabled
  • tool tips appear notifying that an admin must enable the feature

Changelog: added

EE: true

References

Screenshots or screen recordings

Tested in both Saas and Self Managed. Video / screenshots are from self managed:

Admin User:

Non admin user :

How to set up and validate locally

No special setup. Once you have created a user and either set up a paid license or started a trial, Duo should be enabled by default so you will see access to DAP.

If you go and turn of permission for Duo in the settings you will see the above changes. Setting pages:

• Saas group: http://127.0.0.1:3000/groups/[group-name]/-/settings/gitlab_duo/configuration
• SM group: http://127.0.0.1:3000/groups/[group-name]/-/edit#js-gitlab-duo-settings
• Saas / SM project: http://127.0.0.1:3000/[group-name]/[project-name]/edit#js-gitlab-duo-settings

Project

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #585919