Update schema checker to avoid incorrect new required fields checks

[JoelSpeed]

We recently fixed a long standing issue where the schema checker would incorrectly report newly required fields as breaking changes, except, these spurious reports were for fields that had new optional parents, which means that this is actually an acceptable change

/assign @everettraven

[openshift-ci]

Hello @JoelSpeed! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

[everettraven]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: everettraven, JoelSpeed

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [JoelSpeed,everettraven]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[everettraven]

@JoelSpeed for a change like this, presumably a verify bypass is reasonable as this doesn't directly impact the end-user experience with the product?

[JoelSpeed]

/verify bypass

I think so...

As mentioned, this doesn't affect the product in any way, so, lets merge

[JoelSpeed]

/verified bypass

[openshift-ci-robot]

@JoelSpeed: The verified label has been added.

In response to this:

/verified bypass

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@JoelSpeed: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.