feat: support dockercompose language

[dalbitresb12]

This is the same as #9 but for Docker Compose files.

There's issues (see microsoft/vscode-docker#4196, microsoft/vscode-docker#4220) in the Docker extension repository which reference redhat-developer/vscode-yaml#1000, but none of them noticed that the developers of RedHat's YAML extension already closed a similar issue as won't fix.

With this PR, this extension would at least fill the gap that RedHat's extension doesn't (seem to) want to support.

The following lines should be added to the settings.json file, as well as installing the Docker extension:

{
  "[dockercompose]": {
    "editor.defaultFormatter": "bluebrown.yamlfmt"
  }
}

PS.: I had to change the engines.vscode property in package.json for the extension to be packaged. I don't know if you want me to change that for you in this PR or want to do it yourself. Tests might fail due to this.

[bluebrown]

@dalbitresb12 , thanks, the test is passing. What issue did you have with the engine?

[dalbitresb12]

I was getting the following error after running npx vsce package:

@types/vscode ^1.89.0 greater than engines.vscode ^1.80.0. Either upgrade engines.vscode or use an older @types/vscode version

So I had to update engines.vscode to ^1.89.0 to match the version of @types/vscode which was updated in #20.

[dalbitresb12]

Well, you can just ignore me. I was using npx vsce package thinking that it would be the same as running it with npm run package since just using that wasn't working for me in Windows. Turns out it's not the same for some reason. Might be just some weird Windows thing.

I did have to update the package script in package.json from node_modules/.bin/vsce package to vsce package for the script to work without changing engines.vscode.

EDIT:

Well, I was wrong again. It is the same, I had just forgotten that I had already changed engines.vscode to match the types package. Running either npx vsce package or npm run package returns the same error as in my previous comment.

[bluebrown]

So I had to update engines.vscode to ^1.89.0 to match the version of @types/vscode which was updated in #20.

Ok, thanks.