fix(pre-commit-hooks): allow empty ranges in 'commitizen-branch'

Details: Force-pushing a branch back to an older commit pushes no new
         commits, so the range is empty and 'cz check' blocks the push:
> No commit found with range: '...'
         Ignore this error (exit code 3) with '--no-raise 3'.
         Invalid commit messages are still rejected.
---

Signed-off-by: Adrian DC <radian.dc@gmail.com>

Author: AdrianDC

.pre-commit-hooks.yaml

@@ -19,7 +19,7 @@
     the fact (e.g., pre-push or in CI) without an expensive check of the entire
     repository history.
   entry: cz
-  args: [check, --rev-range, "$PRE_COMMIT_FROM_REF..$PRE_COMMIT_TO_REF"]
+  args: [--no-raise, "3", check, --rev-range, "$PRE_COMMIT_FROM_REF..$PRE_COMMIT_TO_REF"]
   always_run: true
   pass_filenames: false
   language: python