fix(build): use known working node version for the installer

[Mairu]

There are errors when using node 21 with nodist -> #266 (comment)
Therefore fixing the node (major) version when building nodist is necessary.

Other changes:

• fix npm links fallback
• fix npm links handling for the installer too
• use matching npm version for node version when building
• GitHub workflows: allow triggering of installer creation without tagging
• fix npm to use the correct version of node (previously fixed node version from the nodist installation directory was used -> could be checked with npm doctor

[nullivex]

Does this actually build the EXE? If so how did you get it to work in the CI environment?

[Mairu]

Yes, the exe is built for tags, and with this MR I added the possibility to trigger the build manually. But this seems only to be possible in the main branch: https://docs.github.com/en/actions/using-workflows/manually-running-a-workflow

The pipeline configuration for building (and create the draft release) is in .github/workflows/release.yml.

[nullivex]

I understand, but is there NSIS support with the needed plugin in the build environment?

[Mairu]

I added a fetch_nsis_plugins.mjs file to download the necessary plugins, NSIS itself is part of the image.

[nullivex]

Great work! That statisfies what I was curious about. I will add my review.

[nullivex]

I have reviewed these changes and asked about considerations I didn't understand when it came to building within the Github workspace. These all seem to be met. The abstraction of the code into lib/build.js is correct and acceptable.

The modifications to the Go code look straightforward and reflect the repository changes.

I see nothing wrong with these changes. I approve.