chore: add new label for stale automation

[dreamorosi]

Description of your changes

This PR introduces a new need-response label that is designed to be used exclusively for the purpose of triggering the stale automation. Issues labeled as need-response that haven't had any interaction in 2 weeks will be marked as stale (status/pending-close-response-required) and subsequently closed as status/rejected after an additional week without interaction.

See the linked issue for full context. Once merged, this PR closes #1389.

Related issues, RFCs

Issue number: #1389

Checklist

• My changes meet the tenets criteria
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding changes to the examples
• My changes generate no new warnings
• The code coverage hasn't decreased
• I have added tests that prove my change is effective and works
• New and existing unit tests pass locally and in Github Actions
• Any dependent changes have been merged and published
• The PR title follows the conventional commit semantics

Breaking change checklist

Is it a breaking change?: NO

• I have documented the migration process
• I have added, implemented necessary warnings (if it can live side by side)

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.