Update package maturity achievements

Why is this change being made?

This MR is reviewing the category maturity targets for the Package stage. It adjusts the maturity targets based on our current capacity and prioritization.

• The container registry is delayed due to the complexity of the registry deployment and migration. We are working cross-functionally with Infrastructure, Delivery, and Distribution to deliver this project, but it is taking longer than expected.
• The package registry is also delayed. As a team, we've been focusing more on scalability and reliability and have not had time to complete the integration work for RubyGems. Or start on RPM. We do have a community contribution in progress for Debian that is getting closer to done. I moved this date back a few milestones.
• The helm chart registry is delayed, but we have an active community contribution in progress and is nearing completion.

Author Checklist

• Provided a concise title for the MR
• Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
• Assign this change to the correct DRI
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
  • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files. (this requirement has been removed pending identification of a new DRI for the handbook)