GitHub Actions - Automate npm package updates and release notes

[codingLogan]

Our workflow currently requires manual changes...

• Determine what version to bump to
• Add the new version notes to CHANGELOG.md
• Add the new version to package.json
• Merge conflicts require manual change and re-approval because of the version number differences

New workflow proposal

• Add conventional commits as a standard, to help generate package releases and versions automatically
• On merge, let semantic-release determine the new version
• On merge, let semantic-release update and tag the package
• On merge, let semantic-release update GitHub/npm with release notes
• Major change - CHANGELOG is no longer update in our codebase (as recommended by semantic-release). GitHub release notes now contain this information.
• Major change - package.json version is no longer updated in our codebase (as recommended by semantic-release). Before publishing to npm, the version is updated compared to the latest git tags.

Reasons

• 👎🏻 We trip over each other's PRs often, and have to seek out re-approvals for PRs that have been tested, but the docs or the version need updating
• 🤖 Automation saves time - As long as we apply the conventional commits correctly
• 😄 Fun - it makes working with the repo more friendly

References

• https://www.conventionalcommits.org/en/v1.0.0/
• https://github.com/semantic-release/semantic-release

[ash-wright123]

LGTM

[github-actions]

🎉 This PR is included in version 0.16.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀