Automate releases in a nicer way

[maybeanerd]

Currently releasing is a manual GitHub release based process that has no direct connection to package.json versions or commit messages

It also forces frontend and backend to have the same version (which might be okay,might be weird)

My idea is:

I don't want every commit to release (as the project is too volatile for that right now)

Have a (manual) pipeline, that when triggered, calculates the new version for both frontend and backend based on conventional commits and bumps their package.json version
Then commit that change and create a GitHub release, triggering the existing release pipeline
https://github.com/release-it/release-it/blob/main/docs/ci.md#github-actions might work for this

A question I don't have answers for yet:
We have two package.jsons, do we want to maintain them seperately? If so, images should also be tagged and released seperately. Seems like a burden, also having both FE&BE on the same version is a nice way to easily see compatability between them, as it's a monorepo.
Can the tooling bump both versions to the same one? If so, that'd be nice