Inconsistent behavior with inlined schemas

Describe the bug

When using the inlined schemas the behavior is different vs when the schema is defined in the settings.

Expected Behavior

The behavior should be the same, doesn't matter if the user sets the schema inline or in configuration.

Current Behavior

The diagnostics do not work or are different.

Steps to Reproduce

1. Start with a blank config and create a file with the following content:

# yaml-language-server: $schema=https://raw.githubusercontent.com/yannh/kubernetes-json-schema/master/v1.22.4-standalone-strict/all.json
apiVersion: networking.k8s.io/v1
kind: Ingress
foo: bar

It doesn't trigger any diagnostics but autocompletion works.

2. Configure the schema to apply to all YAML files in the settings:

{
    "yaml.schemas": {
        "https://raw.githubusercontent.com/yannh/kubernetes-json-schema/master/v1.22.4-standalone-strict/all.json": "/*.yaml"
    }
}

Create a file with the following content:

apiVersion: networking.k8s.io/v1
kind: Ingress
foo: bar

It triggers the expected diagnostics:

• Property foo is not allowed.yaml-schema: https://raw.githubusercontent.com/yannh/kubernetes-json-schema/master/v1.22.4-standalone-strict/_definitions.json

Environment

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

Reproduce the two configurations described in the issue: an inline YAML schema directive and the same schema configured through yaml.schemas. Compare diagnostics while confirming that autocompletion continues to work; done means both schema sources produce the same expected diagnostic for the unsupported foo property.