Add timeout to the rollout status

[benjaminbob21]

• This PR introduces an optional timeout parameter to kubectl operations and rollout status checks
• It also fixes configuration paths must exist error
  This PR fixes issue Feature Request: Allow setting timeout in watching rollout status #350 and builds up on adding timeout to the rollout status #353

[Copilot]

Pull Request Overview

This PR introduces an optional timeout parameter to kubectl operations and rollout status checks, and wires it through deployment, canary, and blue-green strategy helpers, their tests, the GitHub Action entrypoint, and CLI runner.

• Added timeout?: string to checkManifestStability and all Kubectl methods.
• Propagated timeout through strategy helpers (deploySMICanary, deployPodCanary, blue-green helpers, etc.), run.ts, and action inputs.
• Expanded unit tests to verify timeout is passed correctly and updated action.yml and integration workflow accordingly.

Reviewed Changes

Copilot reviewed 26 out of 27 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
src/types/kubectl.ts	Extended Kubectl API with timeout, updated apply, execute, delete, etc.
src/utilities/manifestStabilityUtils.ts	Updated checkManifestStability signature to accept timeout.
src/run.ts	Passes timeout from action input into core commands.
action.yml	Added timeout input definition.
.github/workflows/run-integration-tests...	Added SMI setup step; no timeout-related changes.
Strategy & helper files & tests	Propagated timeout through all strategy helpers and corresponding tests.

Comments suppressed due to low confidence (2)

src/types/kubectl.ts:52

• The timeout flag is being appended here and again in execute, which will produce duplicate --timeout entries. Remove this push and let execute handle adding the timeout argument exactly once.

         if (timeout) applyArgs.push(`--timeout=${timeout}`)

src/types/kubectl.ts:35

• The method currently pushes the entire configurationPaths array as one element. To match test expectations and kubectl syntax, explicitly flatten or join the array (e.g. iterate each path with its own -f flag or comma-join) instead of passing it directly.

   public async apply(

[Tatsinnit]

💡 Thank you so much for the kind ping around this, looks great! please get reviews from @davidgamero and @bosesuneha for any user scenario missed. thank you!

[bosesuneha]

lgtm