Organize extension settings into Sections

[jpogran]

This groups and orders the existing settings into VS Code Setting sections while preserving the exact keys for each setting.

The extension previously utilized different prefixes to indicate different areas like terraform-ls.rootModules or terraform-ls.terraformExecTimeout. This leaves settings in a seemingly random order in the Settings UI and makes it hard to autocomplete inside the json file.

We solve this by organizing the extension settings into sections in the contribute part of the package.json manifest. These sections provide a logical order to extension settings, especially if the extension has many settings or many settings that are nested.

This also allows us to separate out configuration options, like a separate section for Experimental Options:

[radeksimko]

LGTM - thank you for the UX improvement! 🙇🏻‍♂️ 🚀

[radeksimko]

Actually I just opened the JSON file and this came up

[jpogran]

Actually I just opened the JSON file and this came up

It is supposed to be greyed out but still read the settings. It would be greyed out because it's technically not a setting anymore, but still read by VS Code because of the way JSON works.

While this worked in testing, it's too much magic to put in a PR that's purpose is to not affect the user. I have walked this back to just organizing sections and we will work in the terraform.languageServer extraction in a later PR.

[dbanck]

👍

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.