Edit CI workflow to publish releases

[silvanocerza]

On every push of a tag named with a version format:

• Build the project for all supported platforms.
• Create a GitHub release.
  • Builds and checksums are attached as release assets
  • A changelog generated by `arduino/create-changelog from the commit history is added to the release description
  • If the tag has a pre-release version suffix, the GitHub release will be marked as a pre-release.
• Upload the builds to Arduino's downloads server.

The release-go-task.yml added here differs from the standard workflow since this project doesn't need notarization on darwin.

[per1234]

this project doesn't need notarization on darwin

Do you think there will be other projects with the same requirement? If so, I can create a "template" for this flavor of release system. arduino/library-repositories-engine and arduino/library-registry-submission-parser don't need notarization, but they also only need a Linux build, so a different requirement from their release workflow.

[silvanocerza]

Do you think there will be other projects with the same requirement? If so, I can create a "template" for this flavor of release system. arduino/library-repositories-engine and arduino/library-registry-submission-parser don't need notarization, but they also only need a Linux build, so a different requirement from their release workflow.

Yes, other than this project we also have the mdns-discovery and the arduino-language-server.