Add script to generate component changelog entries

[alex-ju]

📌 Summary

This PR proposes a set of changes aiming to automate the component changelog entries.

🛠️ Detailed description

Group component changelog entries in a single markdown file

For illustration, I did this for the components updated in 4.15.0. If agreed I will update the rest of the components.

- @include "partials/version-history/4.15.0.md"
- @include "partials/version-history/4.10.0.md"
+ @include "partials/version-history/version-history.md"

Update the main component changelog to follow convention

Adjusted a few changelog entries in 4.15.0. I propose we follow a one-line format moving forward, as much as possible, to make the automation more reliable:

`Component` - Added `@argument` to `Component::Subcomponent`
`Component` - Fixed something
`Component` - Deprecated `@oldArgument`

Add script to generate component changelog entries

Running the following command in changeset-release/main when preparing to release will append changelog entries to each component, as shown in e4dcdd6.

yarn run generate-component-changelog-entries

Once the component changelogs are generated they can be adjusted as needed before committing to the changeset branch.

🔗 External links

Jira ticket: HDS-4215

---

💬 Please consider using conventional comments when reviewing this PR.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
hds-showcase	✅ Ready (Inspect)	Visit Preview	Dec 18, 2024 11:35am
hds-website	✅ Ready (Inspect)	Visit Preview	Dec 18, 2024 11:35am