chore(image-build): bump apiVersion v1beta1 → v1 for 6 image build tasks

[gferreir]

Changes

API version bump for 6 image build tasks, continuing the v1beta1 → v1 migration tracked in #1381.

Tasks updated

Task	Old → New	Changes
buildpacks	0.6 → 0.7	apiVersion v1, minVersion 0.50.0
docker-build	0.1 → 0.2	apiVersion v1, minVersion 0.50.0
jib-gradle	0.4 → 0.5	apiVersion v1, minVersion 0.50.0
jib-maven	0.5 → 0.6	apiVersion v1, minVersion 0.50.0
ko	0.1 → 0.2	apiVersion v1, minVersion 0.50.0
s2i	0.3 → 0.4	apiVersion v1, minVersion 0.50.0, 2 images pinned

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

Image pinning

s2i was the only task here with hardcoded mutable images. Both were pinned via skopeo inspect:

• s2i step generate: quay.io/openshift-pipeline/s2i:nightly → pinned with @sha256:6c1107bc040ce2b7354c1f101a7e00054bfec754098bd760d846c99dc366662e
• s2i step build: quay.io/buildah/stable:v1.17.0 → pinned with @sha256:a9ebe075cd3232cd2e0d0c5191f3a26272728583ec3beea296838e7ef5a2e543
• buildpacks: helper steps use bash:5.1.4 already pinned by digest; builder via $(params.BUILDER_IMAGE)
• docker-build, jib-gradle, jib-maven, ko: all images provided via task params

Additional changes

• Tests: all 6 tasks have tests, all bumped to v1
• Samples: buildpacks (3 samples), docker-build (1 template), and s2i (2 samples) bumped to v1
• Internal registry dirs: jib-maven/tests/internal-registry/ and s2i/tests/internal-registry/ preserved as-is

Validation

• Zero remaining v1beta1 references across all 6 new version directories (39 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 s2i image pins)
• Original versions untouched
• Single commit, DCO signed

Note on pre-existing conditions

buildpacks, docker-build, jib-gradle, jib-maven, and s2i 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

[tekton-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign vdemeester after the PR has been reviewed.
You can assign the PR to them by writing /assign @vdemeester in a comment when ready.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[gferreir]

/assign @vdemeester