Create GitHub Actions workflow to attach a .msi installer to published releases

[Duckwhale]

I have a prototype for creating MSI installers in my Gists somewhere, but the UX still wasn't great. I need to figure out some things still:

• How to modify the installer package so that it also offers setting the PATH correctly?
• How to add a selection for the install directory?
• How to make sure Windows accepts the release as legitimate (needs to be signed first)?
• What is the best/desired user experience? Compare NodeJS, Python3 installer and many others (Lua's UX is pretty bad in comparison, so let's not copy that approach)

[Duckwhale]

Perhaps NSIS might be a viable alternative, too: https://en.wikipedia.org/wiki/Nullsoft_Scriptable_Install_System

Probably depends on the tools (WIX for MSI is awful to work with); I know electron-builder uses nsis and the result still felt OKish.

[Duckwhale]

As for MSI, some possibly relevant links:

• https://github.com/oleg-shilo/wixsharp
• https://stackoverflow.com/questions/28414986/how-to-create-msi-installer-with-wix/28416931