Draft: Replace "Store all packages in one project" with Artifact Management Group approach

What does this MR do and why?

Summary

This MR updates the package registry workflow documentation to replace the "store all packages in one project" approach with a more practical "dedicated artifact management" structure.

Problem

The current documentation recommends storing all package types in a single GitLab project, which creates several issues:

• Mixed package types make it difficult to apply type-specific policies
• No separation of concerns between different package formats
• Hard to manage cleanup policies, protected packages, and access controls
• Doesn't align with how most enterprises want to organize packages

Solution

New recommended structure:

company/artifact-management/ (top-level group)
├── java-packages/           # Maven packages
├── node-packages/           # npm packages  
├── python-packages/         # PyPI packages
├── docker-images/           # Container registry
├── terraform-modules/       # Terraform modules
├── nuget-packages/          # NuGet packages
└── generic-packages/        # Generic file packages

References

Screenshots or screen recordings

Before	After

How to set up and validate locally

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.