Use openAPIV3Schema from CustomResourceDefinition?

Is your enhancement related to a problem? Please describe.

Given that a lot of projects provide a CRD without a standalone schema, I would like to be able to use the CRD for validation in vscode:

# yaml-language-server: $schema=https://raw.githubusercontent.com/crossplane-contrib/provider-kubernetes/refs/heads/main/examples/in-composition/definition.yaml

There's a schema in the CRD:

spec.versions[].schema.openAPIV3Schema

https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#validation

Describe the solution you would like

Some way to validate using the openAPIV3Schema from a CustomResourceDefinition (CRD).

Describe alternatives you have considered

Extract the schema using tools such as

openapi2jsonschema

Or

crd-to-openapischema

Or manual extraction

    spec:
      versions:
      - name: v1
        schema:
          openAPIV3Schema:
            type: object
            # ... OpenAPI v3 schema definition ...

Additional context

Related to https://github.com/redhat-developer/yaml-language-server/issues/132 ?

Start by reviewing the existing schema validation and schema URL handling in the vscode-yaml extension, then examine the linked yaml-language-server issue. Determine how a CRD's spec.versions[].schema.openAPIV3Schema could be selected and used for validation. Done means a CRD such as the linked definition.yaml can provide validation without manual schema extraction.