ci(github-actions): add check-commit task

[Lee-W]

Description

In #1354, commit check was missed. This PR is to add it back

Checklist

• Add test cases to all the changes you introduce
• Run poetry all locally to ensure this change passes linter check and test
• Test the changes on the local machine manually
• Update the documentation for the changes

Expected behavior

invalid commit should raise an error when running poetry commit-check

Steps to Test This Pull Request

1. randomly create a commit that does not follow conventional commit
2. poetry commit-check

Additional context

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.55%. Comparing base (120d514) to head (768d7cb).
Report is 561 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1357      +/-   ##
==========================================
+ Coverage   97.33%   97.55%   +0.22%     
==========================================
  Files          42       55      +13     
  Lines        2104     2622     +518     
==========================================
+ Hits         2048     2558     +510     
- Misses         56       64       +8     

Flag	Coverage Δ
unittests	97.55% <ø> (+0.22%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Lee-W]

@noirbizarre could you please take a quick look when you have some bandwidth 🙂 This would prevent us from merging PR with wrong commit format accidentally

[noirbizarre]

Note that I thought it was already done by commitizen pre-commit hook:https://github.com/commitizen-tools/commitizen/blob/master/.pre-commit-config.yaml#L50-L56
(and if not, it might be interesting to add this hook)

[Lee-W]

Note that I thought it was already done by commitizen pre-commit hook:https://github.com/commitizen-tools/commitizen/blob/master/.pre-commit-config.yaml#L50-L56 (and if not, it might be interesting to add this hook)

It actually is, but it's also quite common for a new contributor to miss this step (and us to accidentally merge it) so better to add an additional safe guard I think 🤔