[Tracking] `pose/stale-issue-cleanup` not found

[pgavlin]

These repos likely just needs updates to their workflow files. In the future we should avoid deleting actions repos until all dependent repos have been updated.

• Workflow failure: Comment on stale issues pulumi-vault#930
• Workflow failure: Comment on stale issues pulumi-tailscale#822
• Workflow failure: Comment on stale issues pulumi-datadog#1053
• Workflow failure: Comment on stale issues pulumi-kubernetes-coredns#581
• Workflow failure: Comment on stale issues pulumi-gitlab#1089
• Workflow failure: Comment on stale issues pulumi-azuread#2220
• Workflow failure: Comment on stale issues pulumi-kubernetes-cert-manager#806
• Workflow failure: Comment on stale issues pulumi-gcp#3529
• Workflow failure: Comment on stale issues pulumi-consul#799
• Workflow failure: Comment on stale issues pulumi-keycloak#903
• Workflow failure: Comment on stale issues pulumi-nomad#715
• Workflow failure: Comment on stale issues pulumi-azure#3399
• Workflow failure: Comment on stale issues pulumi-mongodbatlas#940
• Workflow failure: Comment on stale issues pulumi-aws#6117

[pose]

Will leave ticket open until we complete the rollout of aws-actions and correct deletion of forked repo.

[pose]

After the update, there is something strange going on where GitHub Workflows are running the latest and greatest action, but somehow fail with a similar error. Example: https://github.com/pulumi/pulumi-kubernetes/actions/runs/21197820169/job/61084790435

Since after retrying it's fixed, I originally thought this was caused by some sort of caching issue. I also noticed that some of the affected repos had old branches which conflicted with the GitHub Workflow (aka "Comment on stale issues" .yml present in other branches pushed to the repo).

I'll attempt to reproduce locally with act and see if I can reliably reproduce the problem.

[pose]

Hit a roadblock since I cannot really reproduce the issue. I created the following PR upstream to see if we can get better stack traces: aws-actions/stale-issue-cleanup#391