[gitlab-org/gitlab] Removing Classic from naming

### ROOT CAUSE The issue is related to the naming conventions used within the GitLab codebase. Specifically, the use of the term "Classic" in referring to certain features (Duo Pro & Duo Enterprise tiers, and non-agentic Chat) needs to be replaced with more precise and accurate terms to avoid confusion and ensure clarity. ### CODE FIX To address this issue, you will need to update the codebase to replace instances of "Classic" with the appropriate terms. Here is a step-by-step guide on how to do this: 1. **Identify the Files to Update:** - Use a search tool within your GitLab repository to find all occurrences of "Classic" in the codebase. This can be done using the search functionality in the GitLab interface or by running a command like `grep -r "Classic" .` in your local repository. 2. **Replace "Classic" with the Correct Terms:** - For Duo Pro & Duo Enterprise tiers: - Replace "Classic" with "Duo Pro" or "Duo Enterprise" as appropriate. - If referring to both tiers together, use "Duo Pro & Duo Enterprise". - For non-agentic Chat: - Replace "Classic" with "Agentic Chat" and "Non-Agentic Chat". 3. **Commit the Changes:** - Create a new branch in your GitLab repository. - Make the necessary changes in the identified files. - Commit the changes with a descriptive message, such as "Replace 'Classic' with 'Duo Pro' and 'Non-Agentic Chat'". 4. **Create a Merge Request:** - Open a merge request from your new branch to the main branch of the GitLab repository. - Provide a detailed description of the changes made and why they are necessary. - Request a review from a team member who can verify the changes. 5. **Review and Merge:** - Once the merge request is reviewed and approved, merge the changes into the main branch. By following these steps, you can ensure that the naming conventions within the GitLab codebase are updated to be more precise and avoid confusion.