feat: new and updated payload examples with resulting schema changes

[wolfy1339]

Resolves #812

---

Behavior

Before the change?

• The schemas were not up to date with real world payloads

After the change?

• Updates the schemas to be up to date with real world payloads

Other information

• Information derived from the OpenAPI spec, and from the example payloads

---

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:

• Feature/model/API additions: Type: Feature

---

[kfcampbell]

How did you go about doing this? How come it wasn't caught by the update script?

[wolfy1339]

The update script is broken because of the switch in the GitHub docs to the OpenAPI spec, and because the examples have been removed.

[wolfy1339]

I have a webhooks endpoint running on my server that compares incoming webhooks to the schema defined in this repo.

It was originally implemented by @G-Rath, as a serverless function to run on Azure, and I modified it to run on express.

https://github.com/G-Rath/compare-gh-webhook-to-schema-function

[octokitbot]

🎉 This PR is included in version 7.1.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀

[G-Rath]

@wolfy1339 fwiw I don't mind migrating the original app to Express/Koa if you like - the serverless function has been shutdown anyway, and it'd give me something to do 🤷