Schema reference in URL hash can’t be resolved

Describe the bug

When a schema uri uses a hash to select a nested schema, the language server can no longer resolve it. This was working in yaml-language-server 1.1.0 and below. It first appeared in 1.1.1.

Expected Behavior

A nested schema can be referenced using a URL hash.

Current Behavior

The following error occurs in VS Code:

[{
	"resource": "/home/remco/Projects/appsemble/apps/person/app-definition.yaml",
	"owner": "_generated_diagnostic_collection_name_#0",
	"code": "768",
	"severity": 8,
	"message": "$ref '%2Fcomponents%2Fschemas%2FAppDefinition' in 'https://appsemble.app/api.json' can not be resolved.",
	"source": "YAML",
	"startLineNumber": 1,
	"startColumn": 1,
	"endLineNumber": 1,
	"endColumn": 2
}]

Steps to Reproduce

1. Create a file named app-definition.yaml.
2. Open it in VS Code
3. Enter at least one character

Environment

• Windows
• Mac
• Linux
• other (please specify) remcohaszing/monaco-yaml#126 (demo)

Start by reproducing the nested-schema URL-hash reference in VS Code and compare behavior between yaml-language-server 1.1.0 and 1.1.1. Trace schema resolution for the encoded hash; the fix is complete when the nested schema resolves without the reported diagnostic.