ci(pyproject.toml): strict check for invalid commit messages

[bearomorphism]

Closes #1493

Description

• Check whether the commit messages of a PR follows Conventional Commits pattern in CI.
• Move check-commit task before cover in poetry all command.

Checklist

• I have read the contributing guidelines

Expected Behavior

Steps to Test This Pull Request

#1495 CI should not pass.

Additional Context

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.92%. Comparing base (d968f26) to head (c18d8aa).
Report is 2 commits behind head on refactors.

Additional details and impacted files

@@            Coverage Diff             @@
##           refactors    #1494   +/-   ##
==========================================
  Coverage      97.92%   97.92%           
==========================================
  Files             58       58           
  Lines           2704     2704           
==========================================
  Hits            2648     2648           
  Misses            56       56           

Flag	Coverage Δ
unittests	97.92% <ø> (ø)

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.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[bearomorphism]

Added poetry run so the command can run on windows platform.

[bearomorphism]

btw it would be great if we can check in this PR after #1457 because there will probably be conflicts and I want to fix the conflicts in this branch.

[Lee-W]

btw it would be great if we can check in this PR after #1457 because there will probably be conflicts and I want to fix the conflicts in this branch.

let's mark it draft then

[Lee-W]

cc @noirbizarre We need this before our GitHub action can check the entire range against the default branch instead of by commits, which contributors might skip.