Fix inconsistent requirement for kind in strict json decoding

[liggitt]

What type of PR is this?

/kind bug

What this PR does / why we need it:

When using non-strict unstructured json decoding, kind and apiVersion are required.

When using strict unstructured json decoding, missing kind and apiVersion were tolerated. This adds tests and makes strict decoding consistent.

Custom resource requests with fieldValidation=Strict consistently require apiVersion and kind, matching non-strict requests

/cc @apelisse @kevindelgado
/sig api-machinery

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: liggitt

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:

• staging/src/k8s.io/apimachinery/pkg/OWNERS [liggitt]
• staging/src/k8s.io/apimachinery/pkg/apis/OWNERS [liggitt]

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

[k8s-triage-robot]

This PR may require API review.

If so, when the changes are ready, complete the pre-review checklist and request an API review.

Status of requested reviews is tracked in the API Review project.

[apelisse]

looks good

[apelisse]

/lgtm
I don't think we'll want to do something about my nit, but in case:
/hold

[kevindelgado]

/lgtm % tests that are now failing because of missing apiVersion

[liggitt]

/hold

hmmm, will dig on those. I verified kind and apiVersion were required when making custom resource requests, but will look at these other uses.

[liggitt]

/hold cancel

the implications of adding the apiVersion requirement to existing decoding paths are bigger than we should tackle here. made strict consistent with non-strict for now, and opened #109023 to track

[apelisse]

Thanks
/lgtm

[kevindelgado]

/lgtm thanks!

[liggitt]

/retest

[cici37]

/triage accepted