build: Add publishing support

[g-bougard]

Hi @redddcyclone

this a PR to add a publishing step.

The purpose here is to rename the generated exe to include the arch in the name. Then a new job is added to download generated artifact and upload them into a one release. This job is triggered when a tag is set and published.

Maybe this job can be merged in the first job to publish each exe (without renaming) in its own release and by only setting the arch in the release name. Let me know what you think.

In place of renaming, maybe the project can be modified to still generate and exe with contains the arch in its name.

This PR is the same than the one I made for our fork. I only removed the code signing step as we use a really private process on which we can't provide more information than what you can read in our workflow ;-)

When the release is made, you may have to edit the release description so it looks prettier, like I did for our own: https://github.com/glpi-project/glpi-agentmonitor/releases/tag/1.0.0

[g-bougard]

Added VirusTotal submission support. To be used, it only needs a token you can obtain from a free VT account which permits 4 API request by minutes if I remember well. The token needs to be set as VT_API_KEY GH Actions secret for the project. Added predefined description.

[g-bougard]

Also added draft & prerelease properties support for the release:

• if the tag contains "test", the release won't be published and it will be kept as draft: this permits to fully test the publishing workflow. You can remove the tag from the repo after the test has passed.
• if the tag contains "beta", the release will be marked as "prelease"

[redddcyclone]

Hi @g-bougard

This is great, thank you very much for this contribution! It's really helpful, especially since I'm still learning my way through GitHub (and Git itself) 😅