Maintenance: remove some issue & PR automation workflows

[dreamorosi]

Summary

Over the past week we've been running some tests to replace some of the workflows to manage issues & PRs current running in GitHub Actions with a dedicated GitHub App.

So far things have worked out fine and we have four features working, that can replace or complement existing workflows:

• close issue comment (example)
• PR acknowledgement section check (example)
• PR related issue check (example)
• help-wanted label on issue (it posts a comment encouraging contributors to leave a comment to claim the issue)

Because of this, we can phase out some of the workflows that were doing these activities.

Why is this needed?

So that we can streamline our maintenance work.

Which area does this relate to?

No response

Solution

No response

Acknowledgment

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

Future readers

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

[powertools-for-aws-oss-automation]

Warning

This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either reopen the issue, or open a new issue referencing this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions]

This is now released under v2.22.0 version!