Remove URL hashes in catalog

[remcohaszing]

The schemas now use an intermediate schema to resolve the hash using a ref.

For more info, see:

• It’s not longer possible to reference schema paths using hashes microsoft/vscode-json-languageservice#123
• Schema reference in URL hash can’t be resolved redhat-developer/yaml-language-server#585
• Lock vscode-json-languageservice@4.1.8 redhat-developer/yaml-language-server#637
• Rejects schemas where $ref refers to $id or $anchor redhat-developer/yaml-language-server#823

[remcohaszing]

Two rules seem to be conflicting here:

1. Schemas using $ref may not specify additional properties
2. Schemas must specify $schema at the top level.

[hyperupcall]

I am not aware of any rules that require $schema at the top level (maybe that is a requirement of the yaml-language-server?), but I was the one that wrote the rule that required no additional properties if $ref was specified. I guess at the time I didn't think top-level $refs could use a hash (which would mean $schema would need to be specified). I originally wrote the rule because sometimes the $schema specified at the top level would be (and sometimes was) different than the schema referenced to with $ref. I suppose to get these changes through you can comment out the local_assert_schema_top_level_$ref_is_standalone rule for now I can fix it later.

On a separate note, are you specifying title in each of the schemas because you need to? I thought that if you specified, say, "title": "Ansible Playbook" on "https://raw.githubusercontent.com/ansible/ansible-lint/main/src/ansiblelint/schemas/ansible.json#/$defs/playbook", you wouldn't need to set title in src/schemas/json/ansible-playbook.json. Since I thought properties (like title and $schema) would "passthrough".

[remcohaszing]

The $schema property is only there to aid schema authors. It’s not needed otherwise. I changed local_assert_top_level_$ref_is_standalone to allow it.

title should be removed indeed.

Now tests fail to resolve a $ref referencing an external URL.

[github-actions]

This PR is stale because it has been open 60 days with no activity. Comment or this will be closed in 7 days.

[remcohaszing]

This issue is still relevant.

[github-actions]

This PR is stale because it has been open 60 days with no activity. Comment or this will be closed in 7 days.

[remcohaszing]

This issue is still relevant.

[github-actions]

This PR is stale because it has been open 60 days with no activity. Comment or this will be closed in 7 days.

[github-actions]

This PR was closed because it has been stalled for 7 days with no activity.

[github-actions]

This PR is stale because it has been open 60 days with no activity. Comment or this will be closed in 7 days.

[github-actions]

This PR was closed because it has been stalled for 7 days with no activity.