Maintenance: revisit stalebot config

[dreamorosi]

Summary

The repo has a stalebot that is supposed to mark issues as stale after a certain amount of time, and then in case of no interaction, close them after a number of days.

We should revisit the configuration of this bot so that it aligns with the current label strategy.

Why is this needed?

Currently the bot is not running properly, although it's being executed every day.

Which area does this relate to?

Automation

Solution

No response

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.