Option to use predefined config file

[kiliantyler]

Instead of creating and reading from a config file in the extension, use an existing .yamlfmt (or yamlfmt.yaml or yamlfmt.yml) file from within the project

This would also require a setting to allow this to override editor settings, for example:

• yamlfmt.yaml exists in folder
• Options in yamlfmt.yaml do not match options set in extension settings
• Extension has an override setting that allows the in-code yamlfmt.yaml to be used

Optionally this could be disabled to force formatting the way the extension is configured.

With no yamlfmt.yaml config file present, extension settings would be used (or global settings, see: #23 )

Presidence (Highest wins):

• .yamlfmt (in folder)
• yamlfmt.yaml (in folder)
• yamlfmt.yml (in folder)
• Global settings (if enabled)
• Extension settings

[kiliantyler]

Option to use predefined config file

[kiliantyler]

Closed with #38