feat: many unrelease endpoint updates

[octokitbot]

If there are any new endpoints, then the code changes will likely required an update of @octokit/types. It should have received a pull request as well, merge & release it first. The @octokit/types should be updated automatically shortly after in this pull request.

Make sure to update the commits so that the merge results in helpful release notes, see Merging the Pull Request & releasing a new version.

In general

• Avoid breaking changes at all costs
• If there are no typescript or code changes, use a docs prefix
• If there are typescript changes but no code changes, use fix(typescript) prefix
• If there are code changes, use fix if a problem was resolved, feat if new endpoints / parameters were added, and feat(deprecation) if a method was deprecated.

[kfcampbell]

The PR description says "avoid breaking changes at all costs", and there is what appears to be several breaking changes for removed endpoints in this PR. I'm unsure what the correct path forward is here.

[wolfy1339]

As a general rule of thumb, a breaking change in types does not always necessarily mean a breaking change in the consumer package.

I'm not entirely well versed on this package and how it works. I would think that a breaking change would be warranted in this case

---

This should probably be documented somewhere
The update process has to go like this for everything to be in sync and work:

1. New release of octokit/openapi
2. New release of octokit/openapi-types
3. New release of octokit/types.ts
4. New release of octokit/plugin-rest-endpoint-methods
5. New release of everything else that depends on these packages

[wolfy1339]

The version of @octokit/est-endpoint-methods needs to be bumped and this should be good to go

[github-actions]

🎉 This PR is included in version 6.0.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀