feat(cli): integrate semantic-release and commitlint for automated ve…

[Thels]

…rsioning and commit validation

• Added semantic-release configuration for automated version management and changelog generation.
• Introduced commitlint with conventional commit format validation to enforce commit message standards.
• Created GitHub Actions workflows for validating commit messages and releasing CLI versions.
• Added a pull request template to guide contributors on commit message formatting and change descriptions.
• Established a changelog file to document notable changes and adhere to semantic versioning.

[Thels]

This PR has both feat and fix - so I'm using it as a nice test bed to see what it does to the version. My understanding from reading the docs is that it takes the "highest impact" change from a given set of changes to determine version increase.

So we shouldn't see jumps from 1.0.0 to 1.0.5

[Thels]

I didn't mean to close it - I clicked comment!

[rocketstack-matt]

@Thels / @markscott-ms what value do we think commitlint is adding? I'm finding it super annoying and don't see anything more useful in the commit comments by following the convention.

[markscott-ms]

The benefit is meant to be automatic bumping of the CLI patch or minor or major version.

When discussed last Thursday it was deemed “let’s try. If it’s annoying people we will back it out”. Let’s talk to @Thels to see if the annoyance threshold has been met.