chore(docs): manually populate changelog for prev versions

[dreamorosi]

Description of your changes

This PR manually populates the changelog files for the last two releases (1.17.0 and 1.18.0).

As detailed in the linked issue, the files were not being updated by lerna and as result the last two releases had no changelog entries (note that this is different from the release notes, which were created correctly).

Since we have established that the changelog is working again (see #2100), we can't troubleshoot the issue as we are unable to reproduce the issue.

I propose to close the topic by filling the gaps and move on.

Related issues, RFCs

Issue number: closes #1982

Checklist

• My changes meet the tenets criteria
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my change is effective and works
• The PR title follows the conventional commit semantics

Breaking change checklist

Is it a breaking change?: NO

• I have documented the migration process
• I have added, implemented necessary warnings (if it can live side by side)

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud