Update release_notes_check.py

[nrichers]

Pull Request Description

What and why?

This PR fixes the outdated auth warning that is causing workflow issues.

How to test

What needs special review?

Dependencies, breaking changes, and deployment notes

Release notes

Checklist

• What and why
• Screenshots or videos (Frontend)
• How to test
• What needs special review
• Dependencies, breaking changes, and deployment notes
• Labels applied
• PR linked to Shortcut
• Unit tests added (Backend)
• Tested locally
• Documentation updated (if required)
• Environment variable additions/changes documented (if required)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Nik Richers seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

PR Summary

This PR updates the authentication method used in the release notes check script. The previous approach initialized the Github API client using only the access token. The updated code now creates an authentication object using the token and passes it to the Github client constructor. This change follows best practices recommended by the Github library, ensuring better security and clearer authentication code structure. Only functional changes have been applied, with no alterations to non-critical files.

Test Suggestions

• Test the script with a valid GitHub access token to ensure that the authentication process is working correctly.
• Verify that the script correctly fetches the repository and pull request details after the changes.
• Simulate an invalid or expired token scenario to test error handling and user feedback.