README: add Windows install instruction for Winget

[kbdharun]

Changes

• Add Windows Install instruction for Winget.

Recently, I added the manifest for soft-serve to Winget. Once new releases are made, I will update the Winget manifest asap. I have referred to glow README for this template.

[bashbunni]

Related: goreleaser/goreleaser#2290

We will likely wait for goreleaser to support winget before updating our docs. I know they're planning on supporting this in the near future, so will keep this open for now as a reminder. That will allow us to ensure that the winget package is automatically updated with each release. Thanks for the nudge!

[kbdharun]

Hi, seems like this PR is GTG. The automation has been added and the recent releases were created by it https://github.com/microsoft/winget-pkgs/pulls?q=is%3Apr+charmbracelet+is%3Aclosed+ .

I have updated the package identifier to reflect the new Moniker.

[bashbunni]

Hey, I know it's been a while. Thank you for this PR, I was just wondering if there's any particular reason why you removed the publisher portion of the package name in this commit? I know nothing about winget, so please don't take this as anything other than me trying to understand how the naming works 😂

[kbdharun]

Hi, Winget supports installing applications via the full package identifier or a unique moniker (which is defined in the locale file). Moniker is a short or alternative name that can be used by an application for easy installation.

i.e. https://github.com/microsoft/winget-pkgs/blob/4d0fcf398afe265216966905f7e6aa3c0a6e3a41/manifests/c/charmbracelet/soft-serve/0.7.3/charmbracelet.soft-serve.locale.en-US.yaml#L12

So instead of specifying the full identifier with publisher i.e winget install charmbracelet.soft-serve you can use winget install soft-serve to install it with ease instead.

In case there is another application with the same name/moniker in future we could switch this back to the full package identifier, currently this would work fine.

[bashbunni]

It looks like we're now using goreleaser to publish our releases, so I'm happy to merge this. I'm just a bit unsure about naming and want to make sure that the package naming is consistent with what gets published to the winget manifest.

Related: https://github.com/microsoft/winget-pkgs/blob/master/manifests/c/charmbracelet/soft-serve/0.7.3/charmbracelet.soft-serve.installer.yaml#L3C20-L3C34