ci: add changelog reminder

[julienrbrt]

Description

Intermediary solution for: #15415
Replaces #15452.

Adding the git cliff config, as it is still useful, for some modules after cleaning up, we should not replace the current process, but this allows us to quickly fix the severely outdated changelog (like math).

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[julienrbrt]

Don't merge yet, I am still testing.

R4R. Updated severely outdated changelog with command like npx git-cliff@latest --include-path "math/**/*.go" --output math/CHANGELOG.md

[github-actions]

@julienrbrt your pull request is missing a changelog!

[tac0turtle]

this is inverting the format, if we go with this we should update the docs.

[julienrbrt]

As this is a generated changelog, it is not supposed to be manually edited, so I think it's fine.
There are a few improvements to be made as discussed with @chatton, I've only added the git cliff to help us when tagging, to quickly verify whether the changelog is ok or not.

[tac0turtle]

its confusing that we have one way here and another elsewhere. Any chance we can decide on one or the other and go with it?

trying to make it consistent

[julienrbrt]

This make sense, lmc how I can update the template!

[julienrbrt]

Updated

[tac0turtle]

thanks