Changelog and versioning

[jbmoelker]

User story

As a developer using Head Start for my project, I want a clear list of changes when there's a newer version of Head Start available, so that I know if it's worth (new features vs breaking changes) updating my project to a newer version.

System design

• [ ] Introduce versioning.
• [ ] Use semantic versioning (major, minor, patch) to indicate the effect of a new version.
• [ ] Use Changesets workflow to track and publish changes to a CHANGELOG.md file.
• [ ] Generate patch files for diff between versions and add those to the source code, so projects using Head Start have a way to upgrade (also see #71 ).

[jbmoelker]

Since Head Start is a starterkit template rather than a package, semver might not be most suitable. As basically every change is an API change. Maybe we can still use Changesets, but with a custom changelog format so our CHANGELOG.md could look something like this:

# Head Start Changelog

## 2024-01-31 <!-- date of merge to main, rather than semver -->

* [#30](https://github.com/voorhoede/head-start/pull/30) adds new Table Block, see its readme for details.
* [#127](https://github.com/voorhoede/head-start/pull/127) fix routing in Preview Mode, ...

## 2024-01-16

* ...