Story (Required)

As a user I am using `auto-configure-new-github-repo` setting and I want to create all the repository CRs to be created in a single namespace.

when `auto-configure-new-github-repo` is set to true, PaC should not create namespace for every repository created on Github and rather the repository CRs must be created inside a single namespace.

Slack thread for context: https://redhat-internal.slack.com/archives/CSPS1077U/p1752848663584889

Background (Required)

when user has thousands of repository on GitHub, with `auto-configure-new-github-repo` enabled, PaC will be create thousands of namespaces and that will be chaos.

Out of scope

Any changes to current namespace template field.

Approach (Required)

Make repository CR name configurable as it has been done for namespace so that repository CRs names will be unique per git repository.

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Mandatory)

• Unit tests must be written for new case
• Docs specifying the new b settings
• E2E test would be better to have

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met