Add validation for exclusiveMinimum

[veepeeaee]

PR to add functionality requested in #20

In addition to existing checks, makes adding exclusiveMinimum: true to a minimum clause a breaking change

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: veepeeaee
Once this PR has been reviewed and has the lgtm label, please assign everettraven for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[everettraven]

While setting exclusiveMinimum and minimum are pretty tightly coupled, I think this would make more sense to be an entirely separate check than integrated as part of the minimum check.

I've historically tried to separate each of these validations to check a singular schema property to keep scope as small as possible until we explicitly need to start coupling checks together to unlock more advanced use cases. Keeping to that pattern for now would be my preference.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale