[gitlab-org/gitlab] Rename "virtual registries" to "virtual repositories" across UI, docs, API

### ROOT CAUSE The issue is a request to rename "virtual registries" to "virtual repositories" across various surfaces of GitLab, including the user interface, documentation, and API. The root cause is a need for terminology consistency with the updated Artifact Management glossary and terminology standards. ### CODE FIX To address this issue, follow these steps: 1. **Audit** all occurrences of "virtual registry" / "virtual registries" across the codebase, UI, docs, and API. 2. **Plan API migration** strategy (aliasing old endpoints, deprecation timeline for old names). 3. **Database migration** assessment (table/column renames or aliases). 4. **Implement** the rename in phases: - **Phase 1**: UI and docs (user-facing, lowest risk). - **Phase 2**: API (with backward-compatible aliases). 5. **Update** all related deprecation notices and release post content. Here is a sample implementation plan: #### Phase 1: UI and Docs 1. **Navigation menu items**: - Update menu items to use "virtual repositories" instead of "virtual registries". - Example: Change "Virtual Registries" to "Virtual Repositories". 2. **Page titles, headings, and breadcrumbs**: - Update titles, headings, and breadcrumbs to use "virtual repositories". - Example: Change "Virtual Registries" to "Virtual Repositories". 3. **Form labels, descriptions, and helper text**: - Update form labels, descriptions, and helper text to use "virtual repositories". - Example: Change "Virtual Registry Name" to "Virtual Repository Name". 4. **Empty states and onboarding copy**: - Update empty states and onboarding copy to use "virtual repositories". - Example: Change "No virtual registries found" to "No virtual repositories found". 5. **Flash messages, alerts, and confirmation dialogs**: - Update flash messages, alerts, and confirmation dialogs to use "virtual repositories". - Example: Change "Virtual registry created successfully" to "Virtual repository created successfully". 6. **Settings pages (project and group level)**: - Update settings pages to use "virtual repositories". - Example: Change "Virtual Registry Settings" to "Virtual Repository Settings". #### Phase 2: API 1. **REST API endpoints**: - Evaluate if URL paths need versioned rename or aliasing. - Example: Change `/api/v4/registries` to `/api/v4/repositories` with a deprecation timeline. 2. **GraphQL types, fields, and mutations**: - Update GraphQL types, fields, and mutations to use "virtual repositories". - Example: Change `virtualRegistry` to `virtualRepository`. 3. **API response payloads and error messages**: - Update API response payloads and error messages to use "virtual repositories". - Example: Change "virtual registry not found" to "virtual repository not found". #### Deprecation Notices and Release Posts 1. **Deprecation notices**: - Update deprecation notices to reference "virtual repositories". - Example: Change "Deprecation of virtual registries" to "Deprecation of virtual repositories". 2. **Release post entries**: - Update release post entries to reference "virtual repositories". - Example: Change "New feature: virtual registries" to "New feature: virtual repositories". By following this plan, you can ensure a smooth transition from "virtual registries" to "virtual repositories" across all relevant surfaces of GitLab.