chore(deps): unpinning semver and updating it

[panther7]

ref #9301

Why?

If one project has the version "7.7.3" and another project has "7.7.2", the bundle package (e.g., Webpack) will include both versions, 7.7.3 and 7.7.2. However, if a project uses ~ or ^, the build will include only one version in the bundle.
This is just one example. If all dependencies have strict versions, all modules with different versions will be included in the bundle. This creates a cascading issue.
If it is not necessary to require a specific version (e.g., for bug fixes, security, etc.), I see no reason to do so.
Using the tilde (~) is a good compromise.

@mmaietta

[changeset-bot]

🦋 Changeset detected

Latest commit: 12c8481

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 9 packages

Name	Type
app-builder-lib	Patch
electron-updater	Patch
dmg-builder	Patch
electron-builder-squirrel-windows	Patch
electron-builder	Patch
electron-forge-maker-appimage	Patch
electron-forge-maker-nsis-web	Patch
electron-forge-maker-nsis	Patch
electron-forge-maker-snap	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	tar@​6.2.1
	semver@​7.7.3

View full report

[panther7]

any update with this?

[mmaietta]

Trying to merge it but every time new commits are pushed, I have to requeue all the CI tests. No more pushes and I can get this into the next release 😅

[panther7]

Ok, only rebase. :-)

Let's go.