fix(nsis): Change the ProgID to a more correct, more unique format

[sabonerune]

fix #9229

Change the format of the ProgID to something more unique.

The format recommended by Microsoft is:

• [Program].[Component].[Version]
• No spaces
• Version portion is optional (but strongly recommended.)
• Have no more than 39 characters.
• Contain no punctuation (including underscores and slashes) except one or more periods.
• Do not start with a digit.

https://learn.microsoft.com/windows/win32/shell/fa-progids#programmatic-identifier-elements-used-by-file-associations
https://learn.microsoft.com/windows/win32/com/-progid--key

In this PR, we set it as follows:

• [Version] is omitted.
  This is useful if you have different versions of the same application installed at the same time, but electron
  -builder doesn't seem to expect this.
• [Program] can contain up to 19 characters from the beginning of the following string.
  • productFilename with invalid characters removed.
  • If productFilename begins with a number, App will be added.
  • If all characters in productFilename are invalid, App${guid} will be used.
• Set [Component] as follows:
  • Fill the ProgID up to 30 characters with ext or name, removing any unusable characters.
  • Finally, remove the hyphens and fill UUID.v5(name || ext, guid) up to the maximum ProgID.

I believe this will allow for the generation of unique ProgIDs while maintaining a certain degree of readability in the registry.

---

Is the Changeset patch correct?
I consider this change an undocumented, detailed behavior change in electron-builder.
However, custom NSIS scripts that expect the ProgID to be name or ext may no longer work correctly.

[mmaietta]

I consider this change an undocumented, detailed behavior change in electron-builder.
However, custom NSIS scripts that expect the ProgID to be name or ext may no longer work correctly.

Based on this comment, this sounds like a Breaking change since we can't guarantee whether other custom NSIS scripts rely on this functionality. Curious on your thoughts? If we're aligned, then this will need to be pushed to the v27 release plans