fix(deps): pin @octokit/core peerDependency to v5

[DanCurryy]

Resolves #717

---

Before the change?

• Octokit/core@6 is now ESM, which while this version is still CJS can't pull in and use.

After the change?

• Pinning this back to Octokit/core@5 where it remains CJS fixes this.

Pull request checklist

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

• Yes
• No

---

[github-actions]

👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

[wolfy1339]

@gr2m @nickfloyd The branch protection rules aren't valid for this branch. I feel like it's matching some generic v*.* matcher and including some workflows that haven't been here for a while

[kfcampbell]

@wolfy1339 I've removed the invalid branch protection checks for the *.x branch protection rule. There are some other 1.x through 6.x rules as well, but hopefully those are far enough back in history they won't be relevant for us. Please let me know if you'd like more changes here!

[github-actions]

🎉 This PR is included in version 10.4.1 🎉

The release is available on:

• GitHub release
• npm package (@release-10.x dist-tag)

Your semantic-release bot 📦🚀