Attach project binaries to releases for accessibility

[holysoles]

This PR serves to address some of the issues with accessing the compiled binaries for this project. By generating releases for this project and attaching binaries to them, it should work around workflow artifacts expiring and any issues with binaries in the repo itself.

Included changes:

• bump the version of the upload-artifact version to a supported one
• change the existing build action to only run on PR events. This includes PRs being opened, additional commits being added to the source branch, etc
• add a new workflow that supports a release workflow

This would require that after merges to master, a maintainer go generate a release for the project, and associated git tag. That will trigger this new workflow and upload the built binaries (unzipped) to the release.

I've tested this on my fork:

• building artifacts upon a PR request being opened
  • also ran a workflow for a subsequent commit
• building and attaching artifacts for a manually generated release

[ayoubfaouzi]

Hello @holysoles

Good stuff ! Thank you.

A couple of suggestion:

• You can safely delete the appveyor.yml, we don't use it anymore
• For the release workflow, we still need to zip the artifacts to avoid detection and potential blocking of the page. You can use the same command in the build workflow to zip it and you can also use the same password.

Once done, I will merge it and make a release. We never made any release so far :)

[holysoles]

@LordNoteworthy thanks for the quick reply! Feedback implemented and I squashed my commits

Example that uses 7z is here: https://github.com/holysoles/al-khaser/releases/tag/v1.0.1

[ayoubfaouzi]

Great work ! I Appreciate the help on this, merging it 🚀