feat: schema generator for basic & advanced configs

[DataM0del]

Description

Adds a schema generator so you can have autocomplete.
To use this in configs, run the generator script and add:

• #:schema ./configuration.schema.json for basic configs
• #:schema ./features.schema.json for advanced configs
  This uses the schema directive in Even Better TOML (linking to the Open VSX registry instead of the normal extension registry because it's outdated on the normal / default Visual Studio marketplace) / Taplo

Testing

Procedure:

• Add the schema directive for each of the config files
• comment out everything below that schema directive so we can test the autocomplete
• Ctrl + Space to trigger the autocomplete.
• Look at the results.

Checklist

Things need to be done before this Pull Request can be merged.

• Initial schemas (not auto-generated)
• Test the schemas
• Make a script to automatically generate these schemas
• Test it
• Change the titles for Basic Configuration and Advanced Configuration to not look like it was generated

[Snowiiii]

Im not sure if this is really necessary, We already have to add config values in the docs it would be really annoying to have to add them in 3 different places

[DataM0del]

Im not sure if this is really necessary, We already have to add config values in the docs it would be really annoying to have to add them in 3 different places

We could auto-generate the docs from these schemas. Obviously you don't get auto complete from the docs, so it's probably better if we do that instead.

[Snowiiii]

Im not sure if this is really necessary, We already have to add config values in the docs it would be really annoying to have to add them in 3 different places

We could auto-generate the docs from these schemas. Obviously you don't get auto complete from the docs, so it's probably better if we do that instead.

I like to have examples and explain in-depth how things work. Which can be done in the docs

[DataM0del]

Im not sure if this is really necessary, We already have to add config values in the docs it would be really annoying to have to add them in 3 different places

We could auto-generate the docs from these schemas. Obviously you don't get auto complete from the docs, so it's probably better if we do that instead.

I like to have examples and explain in-depth how things work. Which can be done in the docs

JSON schemas also have the "example" array in each item, so you can give examples like

"properties": {
  "type": "string",
  "examples": ["yes", "awawhawfrjoiwaojif"]
}

[Snowiiii]

I meant larger and more fancy examples using markdown. Im sorry but i don't really see the point in this PR. We now have split the docs to its eaiser to maintain

[DataM0del]

I meant larger and more fancy examples using markdown. Im sorry but i don't really see the point in this PR. We now have split the docs to its eaiser to maintain

The point of this PR is basically auto-completion.
We could pull the descriptions and etc. from the docs and insert it into the schemas, and maybe insert a link to the docs.
Also, I think most things consuming the JSON schemas are using markdown parsers and then rendering the output HTML anyways.

[DataM0del]

Also, I went through all of the config docs, and it seems to just be a few lists here, maybe a info, warning, tip etc. there, and I don't see any images or anything fancy.

[Snowiiii]

I wonder if it is possible to generate Vitepress sites using json schemas