chore(git-gitlab): bump apiVersion v1beta1 → v1 for 8 git/gitlab tasks

[gferreir]

Changes

API version bump for 8 git and gitlab tasks, continuing the v1beta1 → v1 migration tracked in #1381.

Tasks updated

Task	Old → New	Changes
git-cli	0.4 → 0.5	apiVersion v1, minVersion 0.50.0
git-rebase	0.1 → 0.2	apiVersion v1, minVersion 0.50.0
git-version	0.1 → 0.2	apiVersion v1, minVersion 0.50.0
gitea-set-status	0.1 → 0.2	apiVersion v1, minVersion 0.50.0
gitlab-add-label	0.1 → 0.2	apiVersion v1, minVersion 0.50.0, image pinned
gitlab-set-status	0.2 → 0.4	apiVersion v1, minVersion 0.50.0
create-gitlab-release	0.1 → 0.2	apiVersion v1, minVersion 0.50.0, image pinned
scorecard	0.1 → 0.2	apiVersion v1, minVersion 0.50.0

Each new version was created using copy-then-modify per CONTRIBUTING.md.

Image pinning

Two tasks had hardcoded mutable UBI8 images. Both pinned with digests already resolved via skopeo inspect:

• gitlab-add-label: registry.access.redhat.com/ubi8/ubi:8.2 → pinned with @sha256:d748c21a55796827da82c61f162b505c59451cba24f1874e5185f21275b6bddc
• create-gitlab-release: registry.access.redhat.com/ubi8/ubi-minimal:8.2 → pinned with @sha256:5cfbaf45ca96806917830c183e9f37df2e913b187aadb32e89fd83fa455ebaa6
• git-rebase, git-version, scorecard: images already pinned by sha256 digest
• git-cli, gitea-set-status, gitlab-set-status: image provided via task params

Why gitlab-set-status jumps to 0.4

PR #1324 (open since 2024, needs-ok-to-test) also creates a gitlab-set-status/0.3. That PR adds SSL verification options — a different change from the API bump done here. To avoid a version collision, this PR creates 0.4 directly, skipping 0.3. If #1324 merges at some point, 0.3 would carry its SSL fix on v1beta1, while 0.4 carries the v1 bump. No conflict either way.

Additional changes

• Tests: git-cli, git-version, gitea-set-status, and gitlab-set-status test manifests bumped to v1
• Samples: git-rebase (Pipeline + PipelineRun) and create-gitlab-release samples bumped to v1
• git-rebase PipelineRun: spec.serviceAccountName moved to spec.taskRunTemplate.serviceAccountName per Tekton v1 API
• Test fixtures: gitea-set-status and gitlab-set-status both have tests/fixtures/ directories with mock HTTP responses — preserved as-is (no Tekton apiVersions inside)

Validation

• Zero remaining v1beta1 references across all 8 new version directories (31 files)
• File count matches between old and new versions for every task
• Semantic diff confirms only expected fields changed in task YAMLs (plus the two UBI8 image pins)
• Original versions untouched
• Single commit, DCO signed

Note on pre-existing conditions

git-cli, git-rebase, gitea-set-status, gitlab-add-label, gitlab-set-status, create-gitlab-release, and scorecard interpolate $(params.*) directly in script: blocks.
These patterns are inherited from previous versions and not introduced by this PR.
Script injection hardening will be addressed in a separate batch as part of #1381.

Ref: #1381

/kind cleanup

Submitter Checklist

• Follows the CONTRIBUTING.md guidelines
• Includes tests (if applicable)
• Includes docs (if applicable)
• Commit messages follow commit message best practices

[gferreir]

/assign @vdemeester

[vdemeester]

/lgtm

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [vdemeester]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment