chore: Add PR title conventional commit format check

[bryantbiggs]

What does this PR do?

• Add PR title conventional commit format check

Motivation

• Following the squash and merge pattern, our PR titles become the git commit description which is populated in the GitHub release log. Currently, we don't format our releases for conventional commits, but with this new workflow, we can ensure that PR titles follow conventional commits and better generate both the release name and release notes

Example of conventional commit title:
feat: Add support for 'foo' addon

Example of NOT conventional commit title:
add Support for FOO addon

More

• Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
• Yes, I have added a new example under examples to support my PR
• Yes, I have created another PR for add-ons under add-ons repo (if applicable)
• Yes, I have updated the docs for this feature
• Yes, I ran pre-commit run -a with this PR

Note: Not all the PRs require a new example and/or doc page. In general:

• Use an existing example when possible to demonstrate a new addons usage
• A new docs page under docs/add-ons/* is required for new a new addon

For Moderators

• E2E Test successfully complete before merge?

Additional Notes