docs: format changelogs

[heueristik]

Description

Format changelogs and publishes a new client-common package release (that was not published in #303 because of a wrong PR label being assigned to it).

Type of change

• docs

Checklist:

• I have selected the correct base branch.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• Any dependent changes have been merged and published in downstream modules.
• I ran all tests with success and extended them when possible.
• I have updated the CHANGELOG.md file in the root folder of the package after the [UPCOMING] title and before the latest version.
• I have tested my code on the test network.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information