Allow wildcard URL matching in repository CR

After first coming in contact with the Repository CR I wondered, if it might be feasible to optionally allow url wildcard / prefix matching. This would change the semantics of Repository to something like Repositories.

Use cases:

• Reducing configuration overhead
  • E.g. in an (GitHub) organization context where I trust all members / repositories, I do not have to create a Repository CR for each single repository, which in my case would be managed via GitOps.
• Allowing a common set of custom parameter configurations (which seems to be merged in a recent commit) without copy-paste.
• In the context of this feature request a solution for #934

Notes:

• For the use cases above, I have running a common CI setup in a single namespace in mind. In my organization I do not make use of the auto-configuration of new repositories.

Start by tracing how the Repository CR currently matches repository URLs and review the relationship to issue #934. Define the optional wildcard or prefix semantics, including configuration precedence and matching boundaries; done means the behavior is specified and covered for the stated organization and shared-configuration use cases.