chore(ci): narrow down stale issue filtering (aws-powertools#1346)

* chore: fix issue filtering

* docs: updated maintainer guidance

* docs: updated label meaning

Author: dreamorosi

.github/workflows/stale-issues.yml

@@ -23,13 +23,13 @@ jobs:
           close-issue-reason: not_planned
           # Exempt any issue that hasn't been triaged yet, or that is clearly labeled
           exempt-issue-labels: triage,status/confirmed,status/blocked,status/on-hold,status/completed
-          # Include only issues where any of these labels are present (aka only issues that need more info from the customer)
-          # that are either under discussion, but no info/answer has been provided in 2 weeks, or that were already marked
-          # as stale 
-          any-of-issue-labels: need-more-information,status/discussing,status/pending-close-response-required
+          # Include only issues that were labeled as `need-more-information` (aka only issues that need more info from the customer)
+          only-issue-labels: need-more-information
           # Settings specific to issues
           days-before-issue-stale: 14
           days-before-issue-close: 7
           # Set to ignore PRs
           days-before-pr-stale: -1
-          days-before-pr-close: -1
+          days-before-pr-close: -1
+          # Operations
+          operations-per-run: 60

MAINTAINERS.md

@@ -102,7 +102,7 @@ These are the most common labels used by maintainers to triage issues, pull requ
 | good-first-issue                       | Something that is suitable for those who want to start contributing                            |                                                    |
 | help-wanted                            | Tasks you want help from anyone to move forward                                                | Bandwidth, complex topics, etc.                    |
 | need-customer-feedback                 | Tasks that need more feedback before proceeding                                                | 80/20% rule, uncertain, etc.                       |
-| need-more-information                  | Missing information before making any calls                                                    |                                                    |
+| need-more-information                  | Missing information before making any calls                                                    | Triggers stale automation after 2 weeks            |
 | need-issue                             | PR is missing a related issue for tracking change                                              |                                                    |
 
 ## Maintainer Responsibilities
@@ -268,7 +268,7 @@ In other cases, you may have constrained capacity. Use `help=wanted` label when
 
 When in doubt, use `need-more-information` or `need-customer-feedback` labels to signal more context and feedback are necessary before proceeding. You can also use `status/on-hold` label when you expect it might take a while to gather enough information before you can decide.
 
-Note that issues marked as `need-more-information` and `status/discussing` will be automatically closed after 3 weeks of inactivity.
+Note that issues marked as `need-more-information` will be automatically closed after 3 weeks of inactivity.
 
 ### Crediting contributions
 
@@ -298,4 +298,4 @@ In the rare cases where both parties don't have the bandwidth or expertise to co
 
 ## Automation
 
-🚧 WIP 🚧
+🚧 WIP 🚧