chore(devtools): bump apiVersion v1beta1 → v1 for 5 developer tools tasks

[gferreir]

Changes

API version bump for 5 developer tools tasks, continuing the v1beta1 → v1 migration tracked in #1381.

Tasks updated

Task	Old → New	Changes
pluto	0.1 → 0.2	apiVersion v1, minVersion 0.50.0, image pinned
remote-ssh-commands	0.1 → 0.2	apiVersion v1, minVersion 0.50.0
replace-tokens	0.1 → 0.2	apiVersion v1, minVersion 0.50.0
write-file	0.1 → 0.2	apiVersion v1, minVersion 0.50.0
yq	0.5 → 0.6	apiVersion v1, minVersion 0.50.0

Each new version was created using copy-then-modify per CONTRIBUTING.md.
For yq, only the latest version (0.5) was bumped — earlier versions are superseded.

Image pinning

• pluto: quay.io/fairwinds/pluto:v5 → pinned with @sha256:90eb1a33b99c72d1306318a958d53d101562911138040ee415210e7725a73c22
• remote-ssh-commands, replace-tokens, write-file: images already pinned by sha256 digest
• yq: image provided via $(params.image) with a mutable default (mikefarah/yq:4.47.1). Since it's user-controlled through params, pinning will be addressed separately.

Additional changes

• Tests: pluto, replace-tokens, write-file, and yq test manifests bumped to v1
• Samples: remote-ssh-commands sample bumped to v1
• yq version label: upstream 0.5 had app.kubernetes.io/version: "0.4" — corrected to "0.6" in the new version

Validation

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

Note on pre-existing conditions

yq and remote-ssh-commands 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