Docs - GitLab Duo CLI updates for GA

What does this MR do?

Updates the GitLab Duo CLI docs for GA:

• Removes beta status, adds GA history item
• Removes the pre-req to enable beta features
• Removes the npm package install option
• Removes the note about the CLI being experimental on the flows executor architecture page
• Updates the minimum GitLab version in the pre-reqs
• Adds a note to upgrade to the GA version
• Adds a new "Turn GitLab Duo CLI access on or off" section
• Adds the Duo CLI admin setting to the general turn Duo on and off page.

Related MRs:

• glab docs: docs: updates for GitLab Duo CLI GA (cli!3465 - merged)
• Duo CLI readme and reference docs: docs(cli): updates for Duo CLI GA (gitlab-org/editor-extensions/gitlab-lsp!3615 - merged)

Related issues

Docs: GitLab Duo CLI - GA (#595689 - closed)

Author's checklist

• Optional. Consider taking the GitLab Technical Writing Fundamentals course.
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• If you're adding a new page, add the product availability details under the H1 topic title.
• If you are a GitLab team member, request a review based on:
  • The documentation page's metadata.
  • The associated Technical Writer.

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

• ~"frontend"
• ~"backend"
• ~"type::bug"
• ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

• If the content requires it, ensure the information is reviewed by a subject matter expert.
• Technical writer review items:
  • Ensure docs metadata is present and up-to-date.
  • Ensure the appropriate labels are added to this MR.
  • Ensure a release milestone is set.
  • If relevant to this MR, ensure content topic type principles are in use, including:
    • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
    • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
    • Any task steps should be written as a numbered list.
    • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
• Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.