feat: improve github release process

[lczyk]

github release process is a bit flaky atm. past two releases (1.4.1 and 1.4.1) were missing precompiled binaries which broke a bunch of downstream consumers for a bit. we should improve the github release process such that no release can be published without precompiled binaries.

• Assets missing for 1.4.2 release #307

[lczyk]

(putting thoughts in a comment to keep the issue body focused)

the big suggestion is to keep the release notes in-repo (docs/release-notes/... or something like that) and then have a workflow which automatically build and published a new release on tag push (it would also pick up the release notes from the in-repo committed notes). this would also allow the release notes to go through PR and be reviewed, although i'd suggest the release notes to be mergable with less lengthy review process as to maybe take some pressure from our CTO (ofc requiring such PRs to contain only one new file addition -- the release notes)

🤔 we could even have a workflow which then picks up the tag from that, adds it automatically, obviously checks that its a correct next semver release and publishes the release. this way the new release would just be another PR merge and everything else would happen by itself... maybe that's too much automation for now though..