fix validRef definition to allow for using branches as gitrepository refs

Package Merge Request

Package Changes

(Describe Package changes here)

Package MR

N/A

For Issue

I can write one up if needed, but the problem is pretty self-explanatory. It's not possible to hit a case where the value of <app_x>.git.branch is used as a gitRepository ref because <app_x>.git.tag is checked for first and will always exist.

BB Processes

Add labels for affected packages so that they are deployed in CI as well as a status label:

Be sure to assign to yourself:

Once it is ready for review switch the status and assign reviewers: