Support for k8s v1.23

With introduction of v1.23 in upcoming versions of Harvester, we need to ensure support-bundle-kit simulator supports the same.

Currently a 1.23 bundle fails in simulator due to new GVK's. For example:

FATA[0058] error loading cluster scoped objects error looking up GVR no matches for kind "FlowSchema" in version "flowcontrol.apiserver.k8s.io/v1beta2" for object &{map[apiVersion:flowcontrol.apiserver.k8s.io/v1beta2 kind:FlowSchema metadata:map[annotations:map[apf.kubernetes.io/autoupdate-spec:true sim.harvesterhci.io/creationTimestamp:2022-07-13T06:33:04Z] creationTimestamp:2022-07-13T06:33:04Z generation:1 managedFields:[map[apiVersion:flowcontrol.apiserver.k8s.io/v1beta2 fieldsType:FieldsV1 fieldsV1:map[f:status:map[f:conditions:map[.:map[] k:{"type":"Dangling"}:map[.:map[] f:lastTransitionTime:map[] f:message:map[] f:reason:map[] f:status:map[] f:type:map[]]]]] manager:api-priority-and-fairness-config-consumer-v1 operation:Update subresource:status time:2022-07-13T06:33:04Z] map[apiVersion:flowcontrol.apiserver.k8s.io/v1beta2 fieldsType:FieldsV1 fieldsV1:map[f:metadata:map[f:annotations:map[.:map[] f:apf.kubernetes.io/autoupdate-spec:map[]]] f:spec:map[f:distinguisherMethod:map[.:map[] f:type:map[]] f:matchingPrecedence:map[] f:priorityLevelConfiguration:map[f:name:map[]] f:rules:map[]]] manager:api-priority-and-fairness-config-producer-v1 operation:Update time:2022-07-13T06:33:04Z]] name:catch-all uid:c7391eaa-3b51-484d-8489-65ae64bde007] spec:map[distinguisherMethod:map[type:ByUser] matchingPrecedence:10000 priorityLevelConfiguration:map[name:catch-all] rules:[map[nonResourceRules:[map[nonResourceURLs:[*] verbs:[*]]] resourceRules:[map[apiGroups:[*] clusterScope:true namespaces:[*] resources:[*] verbs:[*]]] subjects:[map[group:map[name:system:unauthenticated] kind:Group] map[group:map[name:system:authenticated] kind:Group]]]]] status:map[conditions:[map[lastTransitionTime:2022-07-13T06:33:04Z message:This FlowSchema references the PriorityLevelConfiguration object named "catch-all" and it exists reason:Found status:False type:Dangling]]]]} 

Start by reproducing the failure in the support-bundle-kit simulator with a Kubernetes v1.23 bundle, focusing on the FlowSchema GVK lookup error shown in the issue. Trace the simulator's resource discovery and mapping path; done means the v1.23 bundle loads without the reported no-matches-for-kind error.