ci: run the full CircleCI suite on rc/1.106.0 every 6 hours

[yuneng-berri]

TLDR

Problem this solves:

• rc/1.106.0 has never had a CircleCI run
• Pushes start nothing and the run-ci label trigger stopped firing

How it solves it:

• Two scheduled workflows run the full suite on rc/1.106.0 every 6 hours
• Main-only job filters also admit rc/1.106.0

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

• I have added meaningful tests
• The handful of test files covering my change pass locally, e.g. uv run pytest tests/unit/<your_test_file>.py -v. Leave the suites (make test-unit-*, make test-unit) to CI: it finishes in ~15 minutes where a laptop takes an hour or more
• My PR passes all required CI/CD checks (e.g., lint, schema.d.ts sync check, etc.)
• My PR's scope is as isolated as possible; it only solves 1 specific problem
• I have received a Greptile Confidence Score of at least 4/5 before requesting a maintainer review (Greptile reviews automatically once the PR is opened; only comment @greptileai to re-request a review after pushing changes)

Screenshots / Proof of Fix

Before (a4fd585)

1. The CircleCI API lists no pipeline for branch rc/1.106.0
2. git show origin/rc/1.106.0:.circleci/config.yml | grep -c 'only: main' prints 27, so even a pipeline there would skip those jobs

After (c5c1cb7)

1. circleci config validate .circleci/config.yml prints Config file at ".circleci/config.yml" is valid.
2. circleci config process shows integration_rc_scheduled with 21 jobs and build_and_test_rc_scheduled with 39 jobs, the same counts as integration and build_and_test, each scheduled on rc/1.106.0 only
3. The first live proof is the scheduled run at the next :39 slot (00:39, 06:39, 12:39 or 18:39 UTC) after merge

Type

🚄 Infrastructure

Caveats (if any)

Medium

• Each scheduled run is a full CircleCI suite, four times a day, until the schedule is removed or the line is retired
• rc/1.106.0 does not have the flaky-test fixes from test: fix stale and flaky tests across CircleCI, GHA and Buildkite #45530, so the known flakes can show up red here

[greptile-apps]

Confidence Score: 5/5

[High impact] The PR appears safe to merge; no actionable failure was found in the scheduled workflows or expanded branch filters

Summary

Adds two scheduled workflows that reuse the full integration and build-and-test job lists on rc/1.106.0 every six hours

• The rc/1.106.0 branch gets scheduled CircleCI suites every six hours.

yuneng-berri explicitly notes that full-suite runs continue four times daily until the schedule is removed or the release line is retired. The author also notes that existing flaky-test fixes are absent from this branch

_{Reviews (1) · Last reviewed commit: "ci: run the full CircleCI suite on rc/1...." · Reviewed by Greptile}