fix: enable stdin on exec. fixes kata containers output

[XT-Phate]

Context

When running the github hook against kata containers, the script output cannot be fetched properly from kata. Only a bit of the stdout/stderr are properly forwarded to GH

Workaround this issue from kata

Resolution

Enabling stdin solves that issue and should not impact other workloads

[Copilot]

Pull Request Overview

Enable stdin forwarding in execPodStep calls to address truncated output when running against Kata containers.

• Pass process.stdin to execPodStep in the Alpine check helper.
• Include process.stdin in the runScriptStep hook invocation.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
packages/k8s/src/k8s/index.ts	Pass process.stdin into execPodStep for the Alpine check
packages/k8s/src/hooks/run-script-step.ts	Forward process.stdin when invoking execPodStep in runScriptStep

Comments suppressed due to low confidence (3)

packages/k8s/src/k8s/index.ts:529

• This change enables passing stdin to execPodStep for Kata containers; consider adding or updating tests to verify that stdin is forwarded correctly in both standard and Kata container environments.

      process.stdin

packages/k8s/src/hooks/run-script-step.ts:30

• Consider adding or updating tests for runScriptStep to ensure that passing process.stdin to execPodStep correctly handles interactive input scenarios, especially with Kata containers.

      process.stdin

packages/k8s/src/hooks/run-script-step.ts:30

• [nitpick] Since multiple callers now explicitly pass process.stdin, consider making process.stdin the default value for the stdin parameter in execPodStep, removing the need for callers to pass it each time.

      process.stdin