fix(docker): use default formatter for yaml and turn off from docker_compose_language_service

[azdanov]

Closes #1309

📑 Description

This should turn off the default formatter from the docker_compose_language_service and use the one specified in the YAML pack to keep it all uniform and prevent double formatting if both packs are used at the same time. I encountered this issue with double formatting, which caused the code to jump up and down near the networks section.

Screencast_20250105_205931.webm

ℹ Additional Information

Maybe there is a better way. Feedback is welcome. 🙂

[github-actions]

Review Checklist

Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:

Proper conventional commit scoping:

• If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin

• If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error

• Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above

• README is properly formatted and uses fenced in links with <url> unless they are inside a [title](url)

• Entry returns a single plugin spec with the new plugin as the only top level spec (not applicable for recipes or packs).

• Proper usage of opts table rather than setting things up with the config function.

• Proper usage of specs table for all specs that are not dependencies of a given plugin (not applicable for recipes or packs).