Github bot update - allow Dapr maintainers to apply labels via bot comments

[WhitWaldo]

Thank you for helping make the Dapr documentation better!

Please follow this checklist before submitting:

• Commits are signed with Developer Certificate of Origin (DCO - learn more)

In addition, please fill out the following to help reviewers understand this pull request:

Description

The bot already allows users of issues to use an "/assign" command to assign themselves an issue if they aren't assigned already. I left that functionality alone and in-place as it applies to all users and works well enough.

But this PR augments that capability. Rather than taking the approach used in other Dapr repos of lists of users, this instead uses a third-party action (I read through the source and see nothing suspicious in there) to determine whether the user that has created the comment is a member of any of the Dapr maintainer org teams.

If so, it executes a separate github-script action that only executes if the following constraints are true:

• The user is a member of any Dapr organization maintainer team
• The comment was made on a PR
• The comment matches any of the allowed comments (listed later on)

If so, the associated label will be appended to the PR if not already present. I read through the labels available in dapr/docs and came up with the following list, which I think is reasonable for maintainers of other repos to want to use:

Slash command	Label
/do-not-merge	do-not-merge
/waiting-on-pr	waiting-on-code-pr
/missing-docs	feature-in-release-no-docs
/required	release-requirement

Finally, I have no idea how to test this out except by committing and giving it a whirl. If anyone has a clue how to otherwise test it, I'm all ears, but I can at least attest to the fact that the Firefox console had no objections to the syntax of the script.

Issue reference

N/A - raised by myself on Discord.

[github-actions]

Stale PR, paging all reviewers

[WhitWaldo]

Don't merge this yet - replacing with another, but when we talked last week, we weren't yet entirely sure which repository to put it in, so this might be superseded by that.