feat(workflow): configure approvers per branch rule

Eugene Harold Krabsrequested to merge
feat/370-branch-approval-rules into main

Plan

  1. Move approver selection into each protected branch rule and derive approval-rule names from branch patterns.
  2. Resolve usernames, groups, and GitLab role tokens while retaining regular approval rules alongside CODEOWNERS.
  3. Update both workflow components, focused regression tests, and usage documentation.

Acceptance criteria

  • The top-level approvers input is removed from both workflow components.
  • Each branch rule accepts its own approvers list.
  • Role tokens such as @@Owner resolve to matching project members.
  • branch replaces name, and renovate/* derives the approval-rule name renovate.
  • CODEOWNERS and regular approval rules can be required together.
  • All focused Git flow and trunk-based unit tests pass.
  • The exact-head merge-request pipeline succeeds.

Closes #370 (closed)

Edited by Eugene Harold Krabs

Merge request reports