docs: adding previous changes in `changelog.d` repository

[clatapie]

Description

As title says, adding previous changes in the changelog.d repository for future patch release.

Issue linked

Not applicable.

Checklist

• [x] I have visited and read Develop PyMAPDL.
• [x] I have tested my changes locally
• [x] I have added necessary documentation or updated existing documentation.
• [x] I have followed the PyMAPDL coding style guidelines.
• [x] I have added appropriate unit tests that also ensure the minimal coverage criteria.
• [x] I have reviewed my changes before submitting this pull request.
• [x] I have linked the issue or issues that are solved to the PR if any.
• [x] I have assigned this PR to myself.
• [x] I have marked this PR as draft if it is not ready to be reviewed yet.
• [x] I have made sure that the title of my PR follows Commit naming conventions (e.g. feat: adding new MAPDL command)

[ansys-reviewer-bot[bot]]

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

@ansys-reviewer-bot review

[clatapie]

I added all those files manually as commits happened prior to https://github.com/ansys/pymapdl/pull/3019

The Release note is built from the changelog.d directory so it should work fine. I will make a test locally before merging this PR.

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 84.47%. Comparing base (7c1eb1e) to head (3179f44). Report is 10 commits behind head on main.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #3182 +/- ## ========================================== - Coverage 86.63% 84.47% -2.17% ========================================== Files 52 52 Lines 9550 9596 +46 ========================================== - Hits 8274 8106 -168 - Misses 1276 1490 +214 ```

[clatapie]

I made some changes in the changelog fragment names as I didn't correctly named them. With no changes, release notes would have rendered as follow:

After having applied the changes, it will render as follow:

[germa89]

I made some changes in the changelog fragment names as I didn't correctly named them. With no changes, release notes would have rendered as follow:

After having applied the changes, it will render as follow:

Is the miscelaneous label ignored on the release changelog?

[clatapie]

Also, to align with the changelog action, I will modify the repository labels:

• Maintenance will become maintenance
• Enhancement will become enhancement
• Dependencies will become dependencies
• BUG will become bug
• etc

Pinging @klmcadams for visibility.

[clatapie]

Is the miscelaneous label ignored on the release changelog?

No, it appears right after the Dependencies section: