feat: Generate Models in OctoKit.GraphQL to introduce new Repository.PlannedFeatures model

[SebastianO1717]

In the following Issue #8414 the work for promoting a repo_plan_features_api was introduced by the following PR #319602

---

Before the change?

Before this PR, the RepositoryPlanFeatures Model did not exists.

After the change?

After this change, the RepositoryPlanFeatures introduced by @talum will be available in the newer versions of the Octokit.GraphQL nuget package.

Pull request checklist

• Tests for the changes have been added (for bug fixes / features) - Integration tests have been ran as per instructions in the following doc

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! 🚀

[SebastianO1717]

A few questions for contributors of the repo:

Is it okay that 50 of the integration tests did not run? If not, is there a way to force these to run through specific configurations?

Image displaying the optional 50 tests that didn't run

Also, I'm open to suggestions in regard to seeing if its possible to generate a smaller set of models. I see there are a lot of changes to them, but on our end we are more focused on the addition of the RepositoryPlanFeatures model being added.

cc: @talum

[nickfloyd]

Is it okay that 50 of the integration tests did not run? If not, is there a way to force these to run through specific configurations?

Hey @SebastianO1717, thanks for this change. Just as a level set, this particular SDK has never made the technical transition out of beta. We were hoping to make that transition after we updated the framework / .NET targets but we deprioritized most of that in favor of focusing on Generative SDKs.

That said, we'd welcome any changes that you'd like to make here but remember there are some rough spots in the implementation (i.e. not all integration tests run - and coverage is a bit low) and generation, as you discovered, is all encompassing and will run for all changes to the GitHub GraphQL schema. The generator also breaks occasionally - there are a number of complexities that exist with generating SDKs from a GraphQL schema.

Again, all things that we would've liked to address, but in favor of a newer more stable approach we decided to set this aside while we see if we can solve the use case that this SDK attempts to fill in a more consistent way.