Invalid missing schema

[jdesrosiers]

We left a TODO to handle the case where a JSON document uses an invalid schemas. I think this should cover that case.

I changed the TestClient to use @hyperjump/uri instead of vscode-uri because the incorrect normalization it does was causing problems with the tests on windows.

[srivastava-diya]

i was wondering since this catch block is empty, a rejected compiledSchema always gets deleted regardless of whether cachedSchemaUri actually depends on schemaUri. For eg. we have 2 unrelated schemas, A (broken) and B (fine), editing B will evict A's cache entry too, resulting in recompile of A the next time it's used, so i just wanted to ask if this is intentional? like is it that a broken entry should get removed whenever anything changes so it can recompile?

[jdesrosiers]

I can't say I completely understand it, but I added a test that shows why it's necessary to clear the cache for invalid schemas. When trying things in the extension host, I'm not seeing any unnecessary recompiles, so I think it's fine. Let me know if you have a better solution.

[srivastava-diya]

Oh got it, i confused it with a different thing, my bad.

[srivastava-diya]

I accidentally merged the style cleanup PR into main before this PR, so I updated the tests in this branch to match, which caused a conflict with main. I've resolved it by rebasing onto main.

If everything looks right to you shall i merge it?