Support issue typed and untyped events

[DavidBoike]

• Resolves [BUG]: IssuesEvent deserialization fails when action=typed #673

---

Before the change?

• Issue events with action typed or untyped would fail to deserialize.

After the change?

• Issue events with action typed or untyped will deserialize correctly, with the type being added/removed available in the root-level Type property, as well as the current type of the issue as a property of the issue.

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)
  • Did not find any docs specifically for issue event subtypes

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

[DavidBoike]

Sorry, this was linked to an internal issue in our org and GitHub got a little overeager to close this.

[DavidBoike]

@JamieMagee because I inadvertantly had an internal PR linked to this one, merging that PR closed this one. That also moved this PR to the Done column in the Octokit Active project board. Would it be possible to get it manually moved back to the Triage status? I don't want to see this PR completely ignored because of that screwup.

[JamieMagee]

@DavidBoike are you able to rebase this PR on top of current main so I can merge it? Or check "Maintainers are allowed to edit this pull request." so I can do it myself.

[DavidBoike]

@JamieMagee I rebased

[DavidBoike]

So @JamieMagee I rebased, then you approved, but in the time it took for CI to run, the branch was no longer up-to-date with main, and now CI won't run until approved again.