use github actions to run the deploy script and make a release

[KrabCode]

ideally whenever a new version number is published in library.properties if the actions can trigger on contents of a text file

if not, any commit to master could rewrite the latest release files

[KrabCode]

maybe it would be easier to always delete the 'latest' tag and create a new release, it's clunky from the UI but it could be easier from the actions API and more robust than trying to edit an existing release..