chore: Update product name and tier availability

Amy Qualls is no longer with GitLabrequested to merge
1976-aqualls-rename-feature-set into main

Description

Addresses two naming problems that are user-facing, but not in traditional documentation files:

  • Epics are available in GitLab Premium and GitLab Ultimate. (Source: https://docs.gitlab.com/user/group/epics/) We phased out GitLab Gold some time ago, and this mention in desktop.package.json was missed.
  • What to call the cluster of Duo-related features in the VS Code settings UI. We currently use GitLab Duo Pro, but Code Suggestions is included in this feature set, and according to https://docs.gitlab.com/user/gitlab_duo/feature_summary/ it's in GitLab Duo Core. We should probably use a tierless version of the name, so we don't have to update this info as often.
Expand for a screenshot of the UI setting

product-name

I'm not 100% confident in the naming, because everything's changing so fast over in devopsai-powered, so I'll add both Suzanne and Steve as reviewers. Steve has merge rights now, HOORAY 🎉

Related Issues

Closes Update VS Code Duo Pro entitlements outside of ... (#1976 - closed)

How has this been tested?

  • If src/browser or src/common has been modified, please consider interoperability with the Web IDE. See Running the Extension in WebIDE.
  • Consider an end-to-end test for significant new features that aren't covered by integration tests.

Screenshots (if appropriate)

What CHANGELOG entry will this MR create?

  • fix: Bug fix fixes - a user-facing issue in production - included in changelog
  • feature: New feature - a user-facing change which adds functionality - included in changelog
  • BREAKING CHANGE: (fix or feature that would cause existing functionality to change) - should bump major version, mentioned in the changelog
  • None - other non-user-facing changes
Edited by Amy Qualls is no longer with GitLab

Merge request reports