fix: revert accidental breaking change in patch release

[wolfy1339]

This reverts commit ed7d1b4.

Resolves #ISSUE_NUMBER

---

Behavior

Before the change?

• The dependency glob was recently updated to v11, that version dropped support for Node versions lower than 20
• Glob is used as a runtime dependency
• Lack of an explicit engines field

After the change?

• Reverts the update to glob to the previous version
• Adds an explicit engines field

Other information

---

Additional info

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)
• Added the appropriate label for the given change

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

• Yes (Please add the Type: Breaking change label)
• No

If Yes, what's the impact:

• N/A

Pull request type

Please add the corresponding label for change this PR introduces:

• Bugfix: Type: Bug
• Dependencies/code cleanup: Type: Maintenance

---

[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 labeled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

[github-actions]

🎉 This PR is included in version 8.1.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀