Maintenance: narrow down stale issue filtering

[dreamorosi]

Summary

The stale issue automation that was set up in #1341 has filter that is too broad and that closes issues that shouldn't be closed.

Examples: #1166, #1179

Why is this needed?

To avoid marking as stale issues that are legitimately waiting on the backlog or the were shelved while waiting for customers input.

Which area does this relate to?

Automation

Solution

We need to narrow down the any-of-issue-label to include only need-more-information and potentially change the key to only-issue-labels.

Acknowledgment

• This request meets Lambda Powertools Tenets
• Should this be considered in other Lambda Powertools languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.