Support automatic removal of needs release notes

[moradology]

This PR updates the Pull Request Labeler configuration to use all/all matching criteria instead of the previous any/any setup for the needs release notes label. This change makes it so that the label is automatically removed when a changes/*.rst file is added/modified in the PR.

Fixes: #2779

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/user-guide/*.rst
• Changes documented as a new file in changes/
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

[moradology]

This is purely CI so I'm not sure it warrants further attention but I'll add to changes/ if that's desirable

[joshmoore]

From my side, not a must but it would test the change 😉

[moradology]

I'm not sure it would. If I'm not mistaken, because labeler uses pull_request_target for permissions reasons, these changes won't be effective on PRs until it's already in the base/target branch

[moradology]

After this is in, maybe someone with perms would be kind of enough to fire off CI for a PR we know should already have its changes/*.rst added

[jhamman]

Looks like this did not work. I'll reopen the issue.

[moradology]

Oh man, there's nothing quite like the developer experience of working on CI and airing all the dirty laundry of a local dev experience in a chain of emails that go out to all maintainers of a project 😭

[d-v-b]

i think without a reliable way to run github actions locally, this iteration has to happen in the open

[joshmoore]

Not saying it's necessarily reliable for this use case, but I have ever had success with https://github.com/nektos/act