docs: add CHANGELOG.md

[lferrigno]

This PR introduces a changelog to the repository, ensuring clear documentation of changes, improvements, and updates across releases. By maintaining a changelog, we aim to:

• Improve Transparency: Provide developers and users with a clear record of new features, fixes, and breaking changes.
• Enhance Collaboration: Enable contributors to stay informed about the evolution of the codebase.
• Facilitate Communication: Easily track progress and updates.

Implementation

• A CHANGELOG.md file has been added at the root of the repository.
• The changelog format adheres to Keep a Changelog guidelines, ensuring consistency and clarity.
• Initial entries include the most recent version and its functionality.

Proposed Workflow

• All PRs introducing new features, fixes, or breaking changes should include a changelog update.
• Use semantic versioning for tracking changes, with clear tags for added, changed, deprecated, fixed, and removed items.

Future Steps

• Update the contribution guidelines to include a section on maintaining the changelog.

[MegaRedHand]

We might be able to autogenerate something similar with https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes
We'd still need to label PRs correctly