Add CI workflow to publish releases

[umbynos]

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

• Build the project for all supported platforms.
• Use gon to sign and notarize the macOS build.
• 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.

[per1234]

I did a test run in my fork with a certificate from my personal Apple developer program account and it worked perfectly:

https://github.com/per1234/cslt-tool/releases/tag/0.0.2

I suggest that we finalize the decision of the naming and location of these files in the arduino/tooling-project-assets repo before merging this, so that the reference URLs and file names of the files added here will be synced with the parent copies when those are added to that repo.

[umbynos]

Rebased to include #13

[per1234]

I suggest renaming release-go-crosscompile-task.yaml to release-go-crosscompile-task.yml.

Either is perfectly valid, and perhaps .yaml is even more "official", but the GitHub Actions documentation and the assets all use .yml, and the other two YAML files added also use .yml, so I think in this case .yml is better.

[per1234]

Since the automated system is in place ready to give itself a validation, I did another fake release in my fork and all is well:

• https://github.com/per1234/cslt-tool/actions/runs/1750488954
• https://github.com/per1234/cslt-tool/releases/tag/0.0.3

Thanks Umberto!

[umbynos]

The release is failing because of the format of the secrets.INSTALLER_CERT_MAC_P12 secret, I'm going to fix the secret and retry the release

[umbynos]

Fixed