Introduce labelers workflow

[justinretzolk]

Community Note

• Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for pull request followers and do not help prioritize the request
• The resources and data sources in this provider are generated from the CloudFormation schema, so they can only support the actions that the underlying schema supports. For this reason submitted bugs should be limited to defects in the generation and runtime code of the provider. Customizing behavior of the resource, or noting a gap in behavior are not valid bugs and should be submitted as enhancements to AWS via the CloudFormation Open Coverage Roadmap.

About

This pull request introduces a new labeler workflow that has similar functionality to what we use in terraform-provider-aws, but has been rewritten quite a bit to try to make it more readable and clean. Since it covered the functionality of two existing workflows, those have been removed. The new workflow will:

• Add prioritized to:
  • issues and pull requests assigned to maintainers
  • pull requests created by maintainers
• Add needs-triage to new issues and pull requests not created by a maintainer
• Add partner to pull requests from partners
• Add external-maintainer to pull requests from Core Contributors
• Remove stale and waiting-response when non-maintainers edit or comment on issues or pull requests
• Remove needs-triage and waiting-response when issues or pull requests are closed

Depends on #1743

[ewbankkit]

LGTM 🚀.

[justinretzolk]

Revised a bit to eliminate the separate job for community checks -- reduces the number of jobs that show up in PR status checks.

[ewbankkit]

LGTM 🚀.