Package Direction updates October 2023

Why is this change being made?

This MR updates the Package direction page and pricing themes for October 2023. This month, I focused on:

• Cleaning up the overall content to remove stale information.
• Update the what's next and why
• Review the maturity targets gitlab-org&2972 to ensure they are populated with the right issues and have the correct due dates in categories.yml.
  • I pushed back the package registry complete date because there is still a lot of work in the epic, gitlab-org&2891, that needs to be completed. There are a lot of key improvements needed for each format. But, in 2023, we resolved most of them for npm, maven, and Nuget. Now we are turning to Terraform, generic and PyPI packages.
  • I pushed back the container registry complete date because there is still a lot of work to in the epic, gitlab-org&2899, that needs to be completed. The biggest hurdle is the self-managed rollout of the next-gen container registry.

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

CHANGEME - add the details saying why, not just what.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (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 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
  • The when to get approval handbook section explains the workflow in more detail
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

---