Document and script the current release process

[nwneisen]

This issue is to document and script the release process that was used when creating v0.3.3 for a future reference.

A longer term solution would be to setup a github action to do everything but I'd like to capture everything known until then.

This is the process I used to create the release binaries on my local machine:

1. Bump the versions in the VERSION and packaging/common.mk files and commit the changes
2. Run the make command for each OS
   make deb
make rpm
make static-linux
make cross-win
make cross-mac
make cross-arm
3. Copy each of the binaries from their output path to a common folder for uploading
4. Verify the binaries are a reasonable size compared to previous releases
5. Create the release using the github release interface. Tag the commit that was a result of step one. Create the release notes using the previous release tag and the new release tag as the range.

Summary:

• Disable .github/workflows/publish.yml so it does not get accidentally triggered or used
• Add a make command or a bash script to generate the release binaries and move them to a common folder for uploading
• Document the process in the project's README.md