Update or remove(if appropriate) incorrect defaults.

[bugadani]

Closes #75 because the root cause of it was an incorrect assumption made from incorrect defaults.

[noppej]

@bugadani Is this a work in progress? I cannot see where in the currently committed code the defaults have been changed.

Also, I wonder if removing the defaults might do more harm than good? Would it not be a better user experience to harmonize the defaults with the probe-rs implementation. That way, launch.json will hint at the correct default.

Finally, if we change the schema, it would be really nice if we can cleanup the appropriate references in the docs. If that is too much to ask, please open an issue against https://github.com/probe-rs/webpage, and I'd be happy to add it to my list.

[Yatekii]

He just synchronized the VSCode config schema with the actual default values we use :)

[noppej]

Github is so strange. I looked at the changes just before typing that comment, and there were no changes to the default in package.json ... just the dependency updates.

I looked again, and they are all there.

[noppej]

The code changes looks fine, and I'm happy to approve. However, if we release this PR, the docs will contradict the product.

[Yatekii]

Tbh, this is the docs. If you configure stuff you look at the autocompletion of vscode :)

[noppej]

I'd be OK if we decide to rip relevant pieces where contradictions exist, from the docs? It makes more sense now that intellisense actually works (courtesy of @bugadani efforts ☺️)

[bugadani]

For some cases the defaults made no sense to me. For example, the SVD path - if it's not set, probe-rs just doesn't use it instead of defaulting to whatever the extension specified. Program binary is required, so a default again makes little sense to me. Forgot to sack npx, sorry about that

[noppej]

Thanks @bugadani ... having "working" intellisense, that gives the "correct" guidance is valuable for usability.