docs(exit_codes): note that --no-raise must precede the subcommand

[bearomorphism]

Description

Adds a placement warning for --no-raise / -nr in docs/exit_codes.md.

--no-raise is registered on the top-level parser (commitizen/cli.py:100-106), so it must appear before the subcommand. Placing it after falls into the unknown-args validator and exits with code 18 (InvalidCommandArgumentError):

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

All existing examples in docs/exit_codes.md already use the correct placement, but the constraint is never stated explicitly. Two recent PRs got it wrong despite the docs being clear by example:

• ci(bump): gracefully handle no bump-eligible commits #1950 — broke the bump workflow on master (failing run; fix in fix(ci): place --no-raise before bump subcommand in bumpversion.yml #1954)
• docs(examples): gracefully handle no bump-eligible commits setup-cz#17 — same mistake in copy-pasteable example workflows

This PR adds a !!! warning "Flag placement" admonition immediately after the flag is introduced, so the rule is impossible to miss when readers skim that section.

Preview

!!! warning "Flag placement"
    `--no-raise` / `-nr` is a **top-level Commitizen flag**, so it must be passed
    **before** the subcommand:

    ```sh
    cz --no-raise 21 bump --yes        # ✅ correct
    cz -nr 21 bump --yes               # ✅ correct (short form)
    ```

    Placing it after the subcommand fails with exit code 18
    (`InvalidCommandArgumentError`):

    ```sh
    cz bump --yes --no-raise 21        # ❌ wrong
    # Invalid commitizen arguments were found: `--no-raise`.
    # Please use -- separator for extra git args
    ```

No code changes; documentation only.

Checklist

• I have read the contributing guidelines

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

Generated-by: GitHub Copilot