Draft: Docs: Rewrite Geo + container registry page for clarity

Zachary Painterrequested to merge
docs/606166-geo-container-registry-docs into master

What does this MR do and why?

Rewrites the Use Geo with the container registry documentation page to improve clarity and comprehension.

Changes:

  • Adds a concept section explaining the Geo + container registry architecture (why each site needs its own external PostgreSQL instance)
  • Adds a setup scenario overview so readers can quickly navigate to the right section
  • Restructures each scenario with clear prerequisites and step-by-step instructions
  • Fixes heading style to follow GitLab docs conventions (task titles use active verb + noun)
  • Reduces inline link density; moves cross-references to a Related topics section
  • Clarifies the distinction between the default (shared) and external metadata database
  • Fixes grammar and style guide issues throughout (removes semicolons, fixes capitalization, uses active voice)

Motivation: User feedback indicated the page was difficult to understand. The page had no concept section, inconsistent prerequisites, and dense inline links that made it hard to follow.

References

  • Issue: #606166
  • Related MR (metadata database pages): to follow

Screenshots or screen recordings

Before After
No architecture explanation; terse intro Concept section explains why each site needs its own database
Inconsistent prerequisites Clear prerequisites per scenario
Dense inline links Related topics section; cleaner body text

How to set up and validate locally

Review the rendered Markdown at: doc/administration/packages/container_registry/using_geo_with_the_container_registry.md

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.

Merge request reports