Schema error when there are both local (path) and remote (URI) schemas that match a file

Describe the bug

VSCode validates YAML files against configured schemas.

Schemas might be local or remote. //Schema paths with or without URI schema

There might be multiple schemas that match a given file.

When there is any number of local schemas that matches a file, the validation works.

When there is a any number of URI-referenced schemas that matches a file, the validation works.

When there is a local schema that matches a file plus any number of URI-referenced schemas, the validation stops working.

Expected Behavior

I expect the validation behavior to be consustent.

Current Behavior

Problems loading reference 'a:/schema.json': Unable to load schema from 'a:/schema.json': No content.YAML(768)

Steps to Reproduce

1. Add a YAML file (e.g. component.yaml) with some valid content
2. Modify VSCode settings to add local schema that matches the file.
3. The file validates against the schema.
4. Modify VSCode settings to add URI-based schema path that matches the file. The URI might be http:// or file://
5. The file immediately stops validating with the following error: Problems loading reference 'a:/schema.json': Unable to load schema from 'a:/schema.json': No content.YAML(768)
6. This error is only thrown for local schemas when there are any other URI-based schemas matching the same file. Additional local schemas do not seem to trigger the issue.

    "yaml.schemas": {
        "A:\\component_spec.json_schema.json": "component.yaml",
        "https://raw.githubusercontent.com/Cloud-Pipelines/component_spec_schema/master/component_spec.json_schema.json": "component.yaml",
        "file:///A:\\component_spec.json_schema.json": "component.yaml",
    }

Environment

• Windows
• Mac
• Linux
• other (please specify)

The issue names no files, tests, or entry points. First reproduce the Windows case with local path and URI schemas, then trace schema loading and URI resolution to identify why the local schema reports no content. Done means matching files validate consistently with local schemas, URI schemas, and both together, without the reported error.