Add commitizen to repo to make it easy to follow conventional-commits

[rikhall1515]

Description

This makes it so that you only need to run 'git commit' in order to get conventional-commit compliant commits.

Validation

Related Issues

Check List

• [x] I have read the Contributing Guidelines and made commit messages that follow the guideline.
• [x] I have run npm run format to ensure the code follows the style guide.
• [x] I have run npm run test to check if all tests are passing.
• [x] I have run npx turbo build to check if the website builds without errors.
• [x] I've covered new added functionality with unit tests if necessary.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
nodejs-org	✅ Ready (Inspect)	Visit Preview	Jun 18, 2024 8:16pm

[rikhall1515]

This is a re-open of #6659 so I'm just currently waiting on this getting approved. Now this PR just has one single commit.

[github-actions[bot]]

Lighthouse Results URL	Performance	Accessibility	Best Practices	SEO	Report
/en	🟠 86	🟢 100	🟢 100	🟢 91	🔗
/en/about	🟢 97	🟢 100	🟢 100	🟢 91	🔗
/en/about/previous-releases	🟢 100	🟢 100	🟢 100	🟢 92	🔗
/en/download	🟢 100	🟢 100	🟢 100	🟢 91	🔗
/en/blog	🟢 100	🟢 100	🟢 100	🟢 92	🔗

[github-actions[bot]]

Unit Test Coverage Report

Lines	Statements	Branches	Functions
	90.67% (593/654)	76.08% (175/230)	94.57% (122/129)

Unit Test Report

Tests	Skipped	Failures	Errors	Time
131	0 :zzz:	0 :x:	0 :fire:	5.192s :stopwatch:

[ovflowd]

Thanks for your patience here and for iterating on this PR!

[bmuenzenmeyer]

The most critical workflow I want to ensure we don't change is the blog post release process. Has anyone tested that yet?

edit: Marco said this would not affect him

[ovflowd]

Alrighty, I believe we can merge this. If issues eventually rise, we can just revert and investigate :)