Handle empty script matches in copilot setup workflow with find

[Copilot]

The Copilot setup workflow failed when no files matched the *-action-*/*/*.sh glob. This change makes the step no-op in that case while still printing matched scripts when present.

• Problem

  • The existing shell glob iteration treated an unmatched wildcard as a literal path, causing the step to fail.

• Change

  • Replaced glob-based for iteration with a find pipeline scoped to ${RUNNER_TEMP} and the same path shape.
  • Kept output behavior unchanged for matched files (echo header + cat content + separator).

• Resulting behavior

  • Zero matches: prints nothing, exits cleanly.
  • One or more matches: prints each script as before.

- run: |
    printenv
    find "${RUNNER_TEMP}" -type f -path "${RUNNER_TEMP}/*-action-*/*/*.sh" | while IFS= read -r script_file; do
      echo "########## $script_file"
      cat "$script_file"
      echo "##############################"
    done

[plengauer]

Hello, thanks for contributing for the first time!

[Copilot]

Pull request overview

Updates the copilot-setup-steps GitHub Actions workflow to avoid failures when the *-action-*/*/*.sh pattern has zero matches, by switching from shell glob iteration to a find-driven loop over ${RUNNER_TEMP}.

Changes:

• Replaced glob-based for iteration with find ... | while read ... to make the step a no-op when there are no matching scripts.
• Preserved the existing per-script log output format (header, file contents, separator).