ci: update workflows

[domire8]

Description

• Revamp build structure #159

This PR solves more items of the parent issue. In particular,

• build-push workflow: deleted since we don't want to build these images anymore
• build-test: don't update version and changelog automatically but check that changelog is updated on PR and check that all versions correspond to each other
• build-release: use same workflow as across other organization repos, check if version was updated and create necessary tags for it (rolling if not updated, [rolling,latest,TAG] if updated)
• doxygen documentation: only on tags, not on push to main

Review guidelines

Estimated Time of Review: 5 minutes

Checklist before merging:

• Confirm that the relevant changelog(s) are up-to-date in case of any user-facing changes

[LouisBrunner]

Why do you update the version in each PR? Is it to see if the CI still works once we merge? Because from a semver POV I don't see the point of creating new identical versions of CL where only the build process (which is invisible to the end-user) has changed.

[domire8]

Why do you update the version in each PR? Is it to see if the CI still works once we merge? Because from a semver POV I don't see the point of creating new identical versions of CL where only the build process (which is invisible to the end-user) has changed.

Is this a question for the status quo or for the future? Currently, the CI requires a version update because we decided so a couple of years ago but I'm exactly removing that in this PR

[LouisBrunner]

Is this a question for the status quo or for the future? Currently, the CI requires a version update because we decided so a couple of years ago but I'm exactly removing that in this PR

Sounds good! 👍

[eeberhard]

Looks great, I just have a suggestion for the generate-docs workflow.

Also, do you know what is going on with the ci/docs branch? Our documentation is pushed to docs and the page is hosted from there, but ci/docs seems to be up to date with main.

[eeberhard]

I think it's still useful to run on main to have the "development" stream documented. It could help us check if doxygen has formatted everything as we expect, especially if we prepare for a minor or major update.

We could call it rolling by moving to doxygen/docs/versions/rolling, and call it latest + vX.Y.Z on tag by making copies. For this you could re-use the "check if version changed" logic in build-release.yml. That would make the list of documented tags on https://aica-technology.github.io/control-libraries/ even nicer to navigate.

[domire8]

The ci/docs branch is the branch name of this PR hehe, sorry for the confusing name.