Update implementation and FAQ regarding Red Hat's YAML extension

[thernstig]

See https://github.com/docker/vscode-extension/blob/main/FAQ.md#i-am-seeing-duplicated-editor-features-such-as-code-completion-suggestions-hover-tooltips-etc-in-compose-files.

This was fixed in redhat-developer/yaml-language-server#1251.

The FAQ should be updated to take the new logic into account.

It specifically also means that one would not need to set docker.extension.enableComposeLanguageServer: true anymore. Until the logic in this repo is fixed, the yaml.schemaDetectionDisableFor will not work by itself.

[rcjsuen]

@thernstig So essentially you're saying conflicts are okay and Red Hat's extension will disable their YAML LSP features for Compose files automatically, right?

[thernstig]

@rcjsuen the details are in redhat-developer/yaml-language-server#1251

The new way to do this is that one would set this if using the RedHat YAML extension:

  "yaml.schemaDetectionDisableFor": [
    // Handled by the Docker DX extensions
    "compose*y*ml",
    "docker-compose*y*ml",
  ],

However please note that in @datho7561 agree it is great DX if the RedHat YAML extension by default can disable itself for certain files, ,if certain extensions (such as Docker DX) is installed. So that all users in all the world do not have to manually update and set the above each time.

But for now, the above solution is the one in place. Let's hope @datho7561 can look into making this even better in the near term.

edit: New issue for this in the RedHhat YAML extension repo, see redhat-developer/vscode-yaml#1251.