docs: instructions for injecting Windows exe metadata

[chroberino]

No description provided.

[Copilot]

Pull Request Overview

This PR adds comprehensive documentation for injecting Windows executable metadata into pkg-generated binaries. The documentation addresses the common issue where packaged executables inherit Node.js binary metadata instead of application-specific information.

Key changes:

• Adds a new section explaining why Windows exe metadata customization is important
• Provides detailed instructions for using resedit to post-process executables
• Includes both Node.js API and command-line usage examples

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

[nitpick] Use an em dash (—) instead of an en dash with spaces (– ) for better typographical consistency.

Suggested change

	[`resedit`](https://www.npmjs.com/package/resedit) also supports command–line
	[`resedit`](https://www.npmjs.com/package/resedit) also supports command-line

[Copilot]

The PowerShell example shows line continuation with backticks, but lacks explanation that this is PowerShell-specific syntax. Consider adding a note that this is PowerShell syntax or provide cross-platform alternatives for bash/cmd users.

[robertsLando]

Considering that there might be users that cross compile this maybe it's worth adding also a linux version of this

[chroberino]

@robertsLando I am not having much experience with Linux binaries, not sure if the same metadata principles will apply there. And especially resedit (which the documented approach is based on) is designed for Windows binaries only:

resedit-js is a library that manipulates resouces contained by Windows Executable files.
(https://www.npmjs.com/package/resedit)

[robertsLando]

@chroberino you may have mis-understood my comment, I simply said that someone may want to cross compile windows binaries on linux and still be able to customize the exe under Linux, so I proposed to create a linux version of rsedit command that actually you did with powershell syntax :)

[chroberino]

Ohhh, got it.
Well, I see two options to address this:

1. Provide two variants of this comand line example which differ only in the line continuation characters (` vs. \)
2. Remove the line continuation characters and make the comand line example a one-liner

Which one do you prefer?

[robertsLando]

I would go for option 1 🙏🏼

[robertsLando]

LGTM