Add automatic application of needs-qa label on PRs to master

[trmartin4]

Type of change

• [ ] Bug fix
• [ ] New feature development
• [ ] Tech debt (refactoring, code cleanup, dependency upgrades, etc)
• [X] Build/deploy pipeline (DevOps)
• [ ] Other

Objective

For PRs against master, we want to enforce a needs-qa label. We currently have an enforce-labels action that will prevent merging if the needs-qa label exists. Currently we rely on the engineer to remember to add it when they create the PR. This action will run on PR creation and automatically add the label.

The equivalent action is already in place on the clients repo.

Code changes

• label-issue-pull-request.yml: New workflow to apply the needs-qa label.

Before you submit

• Please check for formatting errors (dotnet format --verify-no-changes) (required)
• Please add unit tests where it makes sense to do so (encouraged but not required)
• If this change requires a documentation update - notify the documentation team
• If this change has particular deployment requirements - notify the DevOps team

[trmartin4]

Converted to Draft to address linting issues.

[nHFRtfi4Ncs9MmbJALQF9GmwjlWKI3uZTYTxMWA]

Converted to Draft to address linting issues.