Fix: Stop setting build id links for rpm packages

[stopal]

Closes #2303

rpmbuild generates build_id links by default, which are debugging symbols for binaries included in a package. This causes problems between Electron applications which share the same Electron binary, as the debugging symbols conflict with each other.

By disabling the generation of these links i can verify that i can install the resulting rpm package again along with other Electron applications.

See also :

• https://unix.stackexchange.com/questions/411727/what-is-the-purpose-of-usr-lib-build-id-dir
• https://github.com/rpm-software-management/rpm/blob/rpm-4.18.x/macros.in#L470
• RPM: Don't generate build_id links microsoft/vscode#116105

[CLAassistant]

All committers have signed the CLA.

[jeanfbrito]

Hey @stopal, thank you for your contribuition. Did you tested building and installed using the RPM package?
What I need to test it if is working?

[stopal]

Hi @jeanfbrito,
yeah i ran the release npm task to build all packages and installed the resulting RPM package.
I can verify that it doesnt clash with other electron application anymore.

I am running Fedora 36 btw.