Review usage of Semantic Releases

Is the system of Semantic Releases more trouble than its worth? I am a bit of an optimist on the strategy, but others have described it as opaque and too much magic. Should we remove it from our build system?

Pros:

* Automation means releases are near-instant.
* Busywork (e.g. upping the package version, writing release notes) are automated

Cons:

* Requires a commitment to Conventional Commits
* More challenge around understanding what the impact of commit will be (ie what will the be the resultant version change?)
* Many small (single-change) releases (I'm admittedly not sure if this is actually a bad thing)

My urge to is to lean more into the strategy and build in more CI tooling that would:
* reject PRs that don't comply with conventional commit standards (although, I think #25 recently added this)
* comment on a PR informing the user of what the next version will be if the PR is merged.

Thoughts @sharkinsspatial @emileten ?