Declare Drupal 12 compatibility, so a dependent's next-major lane resolves instead of failing on orchestra's core pin

Every orchestra info file declares core_version_requirement: ^11.3, and composer.json requires drupal/core ^11.3. So drupal/orchestra resolves as excluding core 12, and any dependent that pulls orchestra from packages.drupal.org cannot resolve a next-major test lane at all.

Measured in the yoyaku queue on 2026-08-22, on an untouched commit of its default branch. Its composer (next major) job fails before installing anything:

Problem 1
  - Root composer.json requires drupal/orchestra 1.x-dev -> satisfiable by drupal/orchestra[1.x-dev (alias of dev-1.x)].
  - drupal/core 11.3.16 requires drupal/core-composer-scaffold 11.3.16 -> found drupal/core-composer-scaffold[11.3.16] but it conflicts with your root composer.json require (main-dev).

Composer backtracks to core 11.3 because orchestra excludes 12, and then collides with the next-major root's main-dev scaffold requirement. Nothing in the dependent causes that, so the whole Drupal 12 lane is dark for every project built on orchestra.

What is actually unknown

Whether orchestra works on Drupal 12. The project opts into the lane with OPT_IN_TEST_NEXT_MAJOR: 1, but the jobs are manual and have never been run: across the last 60 pipelines, composer (next major) is manual or canceled every time, and the phpstan and phpunit jobs behind it are skipped. Widening the constraint without running them would only move the failure from resolution to runtime.

Proposed steps

• Widen core_version_requirement to ^11.3 || ^12 in every info file, and drupal/core to the same in composer.json, so the lane can resolve and report at all.
• Add the development dependencies that still declare Drupal ^11 (consumers, domain, easy_email, key, simple_oauth, views_bulk_operations, webform) to _LENIENT_ALLOW_LIST, so resolution does not stop on a dependency before orchestra's own code is reached. Drop each entry as that project declares Drupal 12 itself. audit_trail, bpmn_io, eca, kessai and modeler_api already do.
• Take SYMFONY_DEPRECATIONS_HELPER out of the environment on the next-major phpunit job, as kessai does in #3614430: The next-major lane fails every test class on a deprecation the CI template causes, because core 11.5 deprecated setting it at all and core main runs with --fail-on-deprecation unconditionally.
• Run the next-major jobs and fix what they report. Deprecations from the phpstan next-major job come first, since those are the changes core will remove.

One info file, orchestra_payment_route_test.info.yml, declares no core_version_requirement at all. It gets one in the same pass.

AI-Generated: Yes (Claude Code was used to help draft this issue summary and to make the metadata and CI changes. I reviewed them, and the next-major CI lane is what verifies the result.)