Adopt Conventional Commits

[ChristianMurphy]

Hey @UW-Madison-DoIT/uportal-application-framework-committers 👋

I've been thinking lately about how to manage releases, while looking at how other open source projects have been approaching the problem, I came across conventional commits. 👀

The goal the conventional commits standard is to simplify management of semantic versioning. Metadata provided by commit messages is used to guide releases as MAJOR, MINOR, or PATCH.

It seems like the standard could be a good fit with the existing processes and culture at Madison. ⭐
I'd be interested to hear your thoughts on whether adopting conventional commits could be a good idea. 💭

Technical changes in this PR:

• Add commitlint to check commit messages
• Add git hook from husky to trigger commitlint on every change
• Add commitlint config angular, which checks conventional commits, and comes with preset types to use with conventional commits.
• Add commitizen, which provides a CLI for generating conventional commits

Related to uPortal-Attic/uportal-home/pull/666

---

Contributor License Agreement adherence:

• This Contribution is under the terms of Individual Contributor License Agreements (and also Corporate Contributor License Agreements to the extent applicable) appearing in the Apereo CLA roster.

[apetro]

Backlogged MUMMNG-3765 to track in MyUW Scrum allocating MyUW team attention to engaging with this proposal. Should hit the top of the queue no later than end of August.

[vertein]

Just like uPortal-Attic/uportal-home#666, this has my 👍 too.