"Close inactive issues" action, a.k.a. stale.yml needs an update to v9

[ts678]

• I have searched open and closed issues for duplicates.
• I have searched the forum for related topics.

---

Description

Issues are not properly undergoing stale processing, plus there are other problems with v8 that v9 will presumably resolve.
Purging old Github issues is the idea behind this. Labeling of most issues is basically done now, but the action is far behind.

Steps to reproduce

1. Query is:issue is:open sort:updated-asc label:"pending user feedback") -label:stale (and any other disqualifiers, if you like)
2. Look in Actions at "Close inactive issues" run, and see the complaints about Node.js16 going away, operations limits, etc.

• Actual result:
  Stale processing gets far behind, with lots of complaints in its report.
• Expected result:
  Stale processing occurs in a more timely manner without complaints.

EDIT:

v9.0.0 sounds like its stateful nature will eventually cycle through all issues. I'm less confident about v8, as some of them are a month past due on going stale. v9 also fixes the Node.js end of life problem by moving before the planned Spring 2024 cutoff.

Screenshots

Debug log