github/labeler: fix auto-tag backport for .github/actions

[MattSturgeon]

As observed in #482470 (comment), .github/actions/* does not match deeply nested files like .github/actions/checkout/action.yml. Instead, we need a recursive glob like **/*.

Things done

• Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.

[qweered]

Cant we just match everything inside .github?

[MattSturgeon]

Cant we just match everything inside .github?

Maybe, but I'd rather consider that in a dedicated PR.

The primary intent of the auto-tag backport is keeping CI consistent across all supported branches. A secondary benefit is having all changes backported makes conflicts less likely in future backports.

However there may still be some non-ci stuff that is branch-specific in .github/. Also, things like issue forms and PR templates have no effect outside of the default branch.

[nixpkgs-ci]

Backport failed for release-25.11, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release-25.11
git worktree add -d .worktree/backport-482510-to-release-25.11 origin/release-25.11
cd .worktree/backport-482510-to-release-25.11
git switch --create backport-482510-to-release-25.11
git cherry-pick -x cbf9173b1792790683dc19c592a298d224d12e15

[MattSturgeon]

Backport failed for release-25.11, because it was unable to cherry-pick the commit(s).

Ah, I never got round to syncing unbackported labeling changes from master... 🫣