Remove old GitLab version reference

What does this MR do and why?

Remove old GitLab version reference. Discussion on removal in the issue: #443468 (comment 1821831369)

Update 24 files

• /doc/user/packages/npm_registry/index.md
• /doc/user/packages/debian_repository/index.md
• /doc/user/packages/go_proxy/index.md
• /doc/user/packages/pypi_repository/index.md
• /doc/user/packages/nuget_repository/index.md
• /doc/user/packages/terraform_module_registry/index.md
• /doc/user/packages/rubygems_registry/index.md
• /doc/user/packages/helm_repository/index.md
• /doc/user/packages/conan_repository/index.md
• /doc/user/packages/composer_repository/index.md
• /doc/user/packages/generic_packages/index.md
• /doc/user/packages/container_registry/index.md
• /doc/user/packages/dependency_proxy/index.md
• /doc/api/packages/composer.md
• /doc/api/packages/npm.md
• /doc/api/packages/debian_project_distributions.md
• /doc/api/packages/conan.md
• /doc/api/packages/pypi.md
• /doc/api/packages/helm.md
• /doc/api/packages/nuget.md
• /doc/api/packages/rubygems.md
• /doc/api/packages/go_proxy.md
• /doc/api/packages/debian_group_distributions.md
• /doc/api/packages/debian.md

Related issues

Closes #443450 (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 tier badge 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.