docs: clarify winget install command

[osfanbuff63]

winget uses IDs and winget install vscodium might work, but usually it's better to use winget install -e --id VSCodium.VSCodium to make sure it will install the correct package.

[daiyam]

@GitMensch @vedantmgoyal2009 What do you think? I think it's fine as it is.

[GitMensch]

I have no usage-information on winget, so this may be reasonable (I'd personally try "vscodium", not the qualified version).
In general I'd suggest to change the install part to a minimum in that file and instead link to either https://vscodium.com/#install or its source https://github.com/VSCodium/vscodium.github.io/blob/master/_posts/2000-01-05-install.md

[vedantmgoyal9]

As long as any other contributors doesn't play with the manifests and change the Moniker field, it is fine as it is.

[AlexisComix]

From what I have tested, winget install vscodium installs from VSCodium.VSCodium fine. Changing ```bash to ```cmd makes no functional difference because cmd is not recognised by Linguist. However, changing it to something other than bash could be good as Windows does not use bash without WSL. While a change to ```bat or ```batch would also have no visual difference to ```bash, it is recognised by Linguist and would make sense as ```bash may be slightly misleading.

[GitMensch]

Changing ```bash to ```cmd makes no functional difference because cmd is not recognised by Linguist. However, changing it to something other than bash could be good as Windows does not use bash without WSL. While a change to ```bat or ```batch would also have no visual difference to ```bash, it is recognised by Linguist and would make sense as ```bash may be slightly misleading.

I think you've meant the install docs and the code fence used there - I've just changed all three windows entries from "bash" to "cmd".