chore: pin actions to v2.1.0 SHA

[devantler]

Pin all devantler-tech/actions workflow callsites to the latest semver release SHA:
4235593b654b467bb57c2d2f492b1461eab37cba (v2.1.0).

Fixes N/A

Type of change

EOF- [ ] - [ ] - [ ] - [ ] - [x]

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Pins devantler-tech/actions/upsert-issue usages in reporting workflows to the v2.1.0 commit SHA for reproducible GitHub Actions execution and supply-chain safety.

Changes:

• Update upsert-issue action references from an older SHA to 4235593b654b467bb57c2d2f492b1461eab37cba (v2.1.0) in multiple workflows.

Reviewed changes

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

File	Description
.github/workflows/report-repos-with-no-team.yml	Pins upsert-issue action to the v2.1.0 SHA.
.github/workflows/report-repos-with-no-admin-team.yml	Pins upsert-issue action to the v2.1.0 SHA.
.github/workflows/report-repos-with-multi-admin-teams.yml	Pins upsert-issue action to the v2.1.0 SHA.

[Copilot]

Consider keeping the previous descriptive comment (e.g., why this action is used / what it does) and placing the version tag in a consistent format across the repo. Right now the comment changed from a purpose/feature note to only a version label, which reduces local context when scanning workflow steps. A concrete option is to include both purpose and version in the comment (or standardize on # v2.1.0 (upsert-issue) if that’s the repo convention).

Suggested change

	uses: devantler-tech/actions/upsert-issue@4235593b654b467bb57c2d2f492b1461eab37cba # v2.1.0
	uses: devantler-tech/actions/upsert-issue@4235593b654b467bb57c2d2f492b1461eab37cba # upsert-issue v2.1.0

[Copilot]

Same as other workflow: the inline comment now only reflects the version. If these workflows are intended to be self-explanatory, consider preserving a short purpose-oriented note alongside the pinned version so future readers understand the step at a glance.

Suggested change

	uses: devantler-tech/actions/upsert-issue@4235593b654b467bb57c2d2f492b1461eab37cba # v2.1.0
	uses: devantler-tech/actions/upsert-issue@4235593b654b467bb57c2d2f492b1461eab37cba # v2.1.0 - create or update the report issue

[Copilot]

If you’re standardizing action pinning, consider applying a consistent comment style across all callsites (e.g., always # vX.Y.Z or always # <action> vX.Y.Z). This avoids future churn when searching/grepping for pins and makes it easier to audit versions.