Implement language- and content-specific maintainer groups for localization workflows

Currently, we need to modify the CODEOWNERS file every time a **translator needs repository access. This creates unnecessary overhead and maintenance burden.

**translator_ == anyone at GitLab or external / continent worker who can approve and merge marketing translations._

This issue was the result of a DEX/Spartan Weekly meeting, Bookmark here

Proposal: Create a dedicated GitLab group for translators (similar to the existing Tech Docs Maintainers group) to streamline access management.

Specific requirements (based on @mjsibanez 's feedback here #477 (comment 2739188768)):

  1. Blog + The Source:
    • Create a blog-localization group
    • All Localization specialists and Content Managers should have merging rights
    • Members include: Emi, Noriko, Patrick, Laura, Maud, Megumi, Hendrik
  2. Marketing Website:
    • Localization specialists (Emi, Noriko, Laura, Patrick) should be able to add commits to MRs but without merging rights
    • Content Managers (Hendrik, Megumi, Maud) should have merge rights
    • Special consideration: Homepage and pricing page changes should be reviewed by DEX team before merging

Benefits:

  • Eliminates need to update CODEOWNERS for each new translator
  • Centralizes translator access management
  • Reduces administrative overhead

Reference:

Edited by Oleksandr Pysaryuk