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

Frank Mablyrequested to merge
issue/orchestra-3618602:3618602-declare-drupal-12 into 1.x

Declares Drupal 12 compatibility and wires the next-major lane so it can actually report.

  • core_version_requirement: ^11.3 || ^12 in all 44 info files. One of them, orchestra_payment_route_test.info.yml, declared no core requirement at all and now does.
  • drupal/core: ^11.3 || ^12 in composer.json, which is what a dependent's composer resolution reads.
  • README and docs/index.md requirements lines follow.
  • _LENIENT_ALLOW_LIST covers the development dependencies that still declare Drupal ^11 (consumers, domain, easy_email, key, simple_oauth, views_bulk_operations, webform), so the lane resolves far enough to analyze orchestra's own code. The domain entry covers domain_extras, because the template matches the name as a prefix. audit_trail, bpmn_io, eca, kessai and modeler_api already declare Drupal 12 and are not listed.
  • phpunit (next major) takes SYMFONY_DEPRECATIONS_HELPER out of the environment and points the deprecation filter at a new .deprecation-ignore.txt, the same way kessai does in [#3614430]. The ignore file carries a header and no patterns: entries get added only for what the lane actually raises, and only when it belongs to a dependency or to core.

No PHP changes. PHPStan with the deprecation rules over all 727 orchestra PHP files is clean against 11.3.16, there is no unset($transaction) and no setAccessible(), and every functional test class already carries #[RunTestsInSeparateProcesses]. Whatever the next-major jobs report on top of that is the remaining work, and it will land here.

Merge request reports