DOCS: Clean up changelog issues

[SMoraisAnsys]

Description

The first release with changelog content did not run as expected. This should fix part of the changes that were not handled correctly.

Issue linked

None

Checklist

• I have tested my changes locally.
• I have added necessary documentation or updated existing documentation.
• I have followed the coding style guidelines of this project.
• I have added appropriate tests (unit, integration, system).
• I have reviewed my changes before submitting this pull request.
• I have linked the issue or issues that are solved by the PR if any.
• I have agreed with the Contributor License Agreement (CLA).

[ansys-reviewer-bot]

Thanks for opening a Pull Request. If you want to perform a review write a comment saying:

@ansys-reviewer-bot review

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.00%. Comparing base (7c8ba0b) to head (b8cd541).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5962      +/-   ##
==========================================
- Coverage   85.00%   85.00%   -0.01%     
==========================================
  Files         162      162              
  Lines       62603    62603              
==========================================
- Hits        53214    53213       -1     
- Misses       9389     9390       +1     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[MaxJPRey]

Out of curiosity, what was the main reason of the failure?

[SMoraisAnsys]

Out of curiosity, what was the main reason of the failure?

I'm not exactly sure as I wasn't the one doing the release but it seems that the tag was created multiple times and ended up creating multiple version of the file. One of the release failure was associated to setuptools use of metadata version 2.4. For the other one, I don't know.
Also, the overall changelog process was started working in v0.15.2 (and not v0.15.0) and that might be why we faced some drawbacks.