ci(coderabbit-config): refresh the vendored CodeRabbit schema

[cloud-code-bot]

Upstream's CodeRabbit config schema has drifted from the copy vendored here, which is what coderabbit-config-validate.yml grades every enrolled repo against.

⚠️ Tightened maxLength caps — may invalidate existing configs (1):

• chat.integrations.jira.issue_template: uncapped → 3000

Added properties (2):

• chat.integrations.jira.issue_template
• reviews.tools.ruff.config_file

Before merging, check the tightened-cap section above if there is one: a lowered maxLength retroactively invalidates configs nobody has touched, and merging this makes their next PR red. Landing the cleanup alongside is usually the right order.

Warning

The invariant unit suite FAILS against the proposed schema (this run). That suite asserts the exact facts the checker's messages rest on, so this is the signal to read closely, not a flake: either the schema change is one we must adapt the checker and its tests to, or the fetch is not what we think it is. Update those assertions in this PR, deliberately, before merging.

Invariant suite output

...................................................................F.............................F.
======================================================================
FAIL: test_the_two_halves_partition_the_objects_that_declare_properties (test_check_coderabbit_config.OpennessTest.test_the_two_halves_partition_the_objects_that_declare_properties)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/runner/work/github-workflows/github-workflows/.github/coderabbit-config/tests/test_check_coderabbit_config.py", line 1060, in test_the_two_halves_partition_the_objects_that_declare_properties
    self.assertEqual(len(omitted), 104)
AssertionError: 105 != 104

======================================================================
FAIL: test_the_committed_schema_has_the_documented_cap_set (test_schema_drift.VendoredSchemaTest.test_the_committed_schema_has_the_documented_cap_set)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/runner/work/github-workflows/github-workflows/.github/coderabbit-config/tests/test_schema_drift.py", line 213, in test_the_committed_schema_has_the_documented_cap_set
    self.assertEqual(len(caps), 14)
AssertionError: 15 != 14

----------------------------------------------------------------------
Ran 99 tests in 2.586s

FAILED (failures=2)

Merging this touches .github/coderabbit-config/**, which triggers bump-coderabbit-config-callers.yml and rolls the SHA-pinned caller fleet forward.

Opened by the refresh-coderabbit-schema workflow.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 46e8b66b-755b-4185-b750-2d11c09e8c23

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}