fix(examples): place --no-raise before bump subcommand

`--no-raise` is a top-level commitizen option, so it must appear
before the `bump` subcommand. With it placed after, argparse treats
`--no-raise 21` as unknown trailing arguments and the CLI exits with
code 18 (`INVALID_COMMAND_ARGUMENT`):

    Invalid commitizen arguments were found: `--no-raise`.
    Please use -- separator for extra git args

This is what failed the bump workflow on commitizen-tools/commitizen
master in run 25542335831, which copy-pasted the same pattern from
these examples.

Move the option before `bump` in both examples and add a comment so
future readers do not repeat the mistake.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: 2 people

examples/bump-release.yaml

@@ -23,9 +23,11 @@ jobs:
       - id: bump-version
         run: |
           old_sha="$(git rev-parse HEAD)"
-          # Pass --no-raise 21 so that pushing only non-bump-eligible commits
-          # (e.g. docs:, ci:, build(deps):) does not fail the workflow.
-          cz bump --yes --annotated-tag --no-raise 21
+          # Pass `--no-raise 21` so that pushing only non-bump-eligible commits
+          # (e.g. docs:, ci:, build(deps):) does not fail the workflow. Note
+          # that `--no-raise` is a top-level option and must come before the
+          # `bump` subcommand. Exit code 21 is NO_COMMITS_TO_BUMP.
+          cz --no-raise 21 bump --yes --annotated-tag
 
           if [ "$(git rev-parse HEAD)" = "$old_sha" ]; then
             echo "No bump-eligible commits found, skipping release."

examples/trigger-other-job/.github/workflows/bump-release.yaml

@@ -24,9 +24,11 @@ jobs:
         run: |
           old_version="$(cz version -p)"
           old_sha="$(git rev-parse HEAD)"
-          # Pass --no-raise 21 so that pushing only non-bump-eligible commits
-          # (e.g. docs:, ci:, build(deps):) does not fail the workflow.
-          cz bump --yes --annotated-tag --no-raise 21
+          # Pass `--no-raise 21` so that pushing only non-bump-eligible commits
+          # (e.g. docs:, ci:, build(deps):) does not fail the workflow. Note
+          # that `--no-raise` is a top-level option and must come before the
+          # `bump` subcommand. Exit code 21 is NO_COMMITS_TO_BUMP.
+          cz --no-raise 21 bump --yes --annotated-tag
 
           if [ "$(git rev-parse HEAD)" = "$old_sha" ]; then
             echo "No bump-eligible commits found, skipping release."