Update composer documentation: fix the ssh access version history

🎈 Context

In Enable the ssh access by default in the Compose... (!132147 - merged), we enabled by default the composer_use_ssh_source_urls feature flag along with the version history in the documentation .

The idea was that the MR could get included in %16.4. Well, that plan failed 😸

That's ok, this means that the change is delivered in %16.5 . Still, the documentation version history needs to be fixed to be accurate. That's the goal of this MR.

🤔 What does this MR do?

• Update the version history of the composer package registry ssh access docs.

See: https://docs.gitlab.com/ee/user/packages/composer_repository/#ssh-access

🥂 Related issues

• Include ssh-based urls in composer metadata sou... (#329246 - closed)
• [Feature flag] Rollout of `composer_use_ssh_sou... (#422171 - 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 or changing the main heading of the page (H1), ensure that the product tier badge is added.
• 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.