Build name convention standardization

[efb4f5ff-1298-471a-8973-3d47447115dc]

Build name convention standardization

Pull Request Type

• Bugfix
• Feature Implementation
• Documentation
• Other

Related issue

#6415

Description

This PR changes the following:

• We were using a mix match of hyphens and underscores so this changes all builds to use hyphens instead of underscores. Why hyphens? Most release builds were using hyphens and for nightly builds it was about 50/50 so i opted for hyphens as most normal users (the ones that use release builds) are used to seeing hyphens.
• Some build names didnt include the .zip extension so i added them
• if file name contains portable then the following structure is used, platform-architecture-portable. There was a mix of this structure and platform-portable-architecture being used.

Additional context

I will create a PR for our website that will pull the now adjusted release builds. That PR will be drafted as it should be merged right before release.

This is part 2 of making changes in these workflow.
Upcoming parts:

• Part 3: Group all builds based on platform
• Part 4: Investigate if all builds have .zip and .7z equivalents

[absidue]

We should probably stick with underscores for the artifacts that electron-builder also uses underscores e.g. the deb files where using underscores to separate the name, version and architecture in the deb file name is a convention .