Create pr-status-labels.yml action

[roaksoax]

What does this PR do?

Adds a new (test) action to automatically label PRs based on their review status, e.g.:

status:needs-triage
status:approved
status:on-hold
status:needs-review

Why is it important/What is the impact to the user?

It does not impact the user but helps automatically label PR's based on their status.

Checklist

• My code follows the style guidelines of this project
  - [ ] I have commented my code, particularly in hard-to-understand areas
  - [ ] I have made corresponding changes to the documentation
  - [ ] I have made corresponding change to the default configuration files (and/or docker env variables)
  - [ ] I have added tests that prove my fix is effective or that my feature works

[robbavey]

Some nits/comments.

[robbavey]

enable-welcomemessage would need to true for this to be displayed

[roaksoax]

Yes, it's intentionally disabled for the time being. The only thing that this is doing is the labeling.

[robbavey]

Do we need these settings if merge automation is disabled?

[roaksoax]

We do. On my testing, for some reason the labeler part didn't work without having all the settings in the config, even if there were default settings by the action itself already set.

[robbavey]

lgtm

[mergify]

This pull request does not have a backport label. Could you fix it @roaksoax? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
• backport-8.x is the label to automatically backport to the 8.x branch.

[mergify]

backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label.