Align Commit Message Format with Community Standards

[lasuk]

Our new standards for commit messages introduced in b5c5ee87060 do not match the usual recommendations in other projects. As a result, the messages display poorly in fork, a widely used git client.

I propose to align our commit messages with the standard community format, nicely summarised by freecodecamp as:

<Summarize change(s) in around 50 characters or less>

<More detailed explanatory description of the change wrapped into about 72
characters>

A few pointers on the topic from the first page of google results:

• https://www.freecodecamp.org/news/writing-good-commit-messages-a-practical-guide/
• https://gist.github.com/robertpainsi/b632364184e70900af4ab688decf6f53
• https://ec.europa.eu/component-library/v1.15.0/eu/docs/conventions/git/

[lasuk]

It would be worthwhile to check as well whether other naming conventions introduced in b5c5ee8706 align with community standards. Maybe ChatGPT can help with this.