[wip] yaml unmarshal for OpenAPIv3 types

[alexzielenski]

This PR mirrors #279 but for the OpenAPI v3 types.
Motivatoin/detials are in that issue

Benchmark Results
From: https://github.com/alexzielenski/kube-openapi-gnostic-benchmark

Using JSON:

BenchmarkSlowConversionV3
BenchmarkSlowConversionV3/json->kube
BenchmarkSlowConversionV3/json->kube-8         	       2	 585903594 ns/op	149246568 B/op	 1835197 allocs/op
BenchmarkSlowConversionV3/json->gnostic
BenchmarkSlowConversionV3/json->gnostic-8      	       4	 290851778 ns/op	116498218 B/op	 1528737 allocs/op
BenchmarkSlowConversionV3/gnostic->pb
BenchmarkSlowConversionV3/gnostic->pb-8        	      72	  15533586 ns/op	 4304896 B/op	      47 allocs/op
BenchmarkSlowConversionV3/pb->gnostic
BenchmarkSlowConversionV3/pb->gnostic-8        	      58	  19689780 ns/op	14967265 B/op	  170123 allocs/op
BenchmarkSlowConversionV3/gnostic->json
BenchmarkSlowConversionV3/gnostic->json-8      	      50	  24571630 ns/op	 5867870 B/op	      47 allocs/op
BenchmarkSlowConversionV3/json->kube#01
BenchmarkSlowConversionV3/json->kube#01-8      	       2	 625525483 ns/op	149450440 B/op	 1835730 allocs/op

In total a conversion from

PB -> Gnostic -> JSON -> Kube-OpenAPIv3 was approx 670ms

Using YAML:

BenchmarkFastConversionV3
BenchmarkFastConversionV3/json->kube
BenchmarkFastConversionV3/json->kube-8         	       2	 573242620 ns/op	149247712 B/op	 1835203 allocs/op
BenchmarkFastConversionV3/json->gnostic
BenchmarkFastConversionV3/json->gnostic-8      	       4	 294514478 ns/op	116470526 B/op	 1528736 allocs/op
BenchmarkFastConversionV3/gnostic->pb
BenchmarkFastConversionV3/gnostic->pb-8        	      69	  16159228 ns/op	 4304929 B/op	      47 allocs/op
BenchmarkFastConversionV3/pb->gnostic
BenchmarkFastConversionV3/pb->gnostic-8        	      64	  19036357 ns/op	14967267 B/op	  170123 allocs/op
BenchmarkFastConversionV3/gnostic->yaml
BenchmarkFastConversionV3/gnostic->yaml-8      	      31	  44807695 ns/op	37846702 B/op	  388852 allocs/op
BenchmarkFastConversionV3/yaml->kube
BenchmarkFastConversionV3/yaml->kube-8         	      14	  87296806 ns/op	37919867 B/op	  733867 allocs/op

In total a conversion from

PB -> Gnostic -> YAML -> Kube-OpenAPIv3 was approx 151ms

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: alexzielenski
To complete the pull request process, please assign sttts after the PR has been reviewed.
You can assign the PR to them by writing /assign @sttts in a comment when ready.

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

Needs approval from an approver in each of these files:

• OWNERS
• pkg/validation/OWNERS

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

[alexzielenski]

/assign @Jefftree

[k8s-triage-robot]

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

This bot triages issues and 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 issue is closed

You can:

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

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

/lifecycle stale

[k8s-triage-robot]

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

This bot triages issues and 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 issue is closed

You can:

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

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

/lifecycle rotten

[k8s-triage-robot]

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

This bot triages issues and 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 issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close

[k8s-ci-robot]

@k8s-triage-robot: Closed this PR.

In response to this:

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

This bot triages issues and 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 issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close

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/test-infra repository.