Update symfony/console to Symfony 6

Composer 2.3 has a Pre-release which should be testable according to this: https://github.com/composer/composer/issues/10573

I've created an MR which "merely" changes "composer/composer": "^2.2.4", to "composer/composer": "dev-main", in composer.json and "symfony/console": "^5.4", to "symfony/console": "^6.0", in core/composer.json.

Doing a composer update composer/composer -W afterwards gives:

  - Upgrading composer/composer (2.2.6 => dev-main 575fbfb)
  - Upgrading composer/pcre (1.0.1 => 3.0.0)
  - Upgrading composer/xdebug-handler (2.0.4 => 3.0.3)
  - Upgrading drupal/core (10.0.x-dev 343695d => 10.0.x-dev 7c05be6)
  - Upgrading symfony/console (v5.4.3 => v6.0.5)
  - Upgrading symfony/filesystem (v6.0.3 => v6.0.5)
  - Upgrading symfony/polyfill-ctype (v1.24.0 => v1.25.0)
  - Upgrading symfony/polyfill-intl-grapheme (v1.24.0 => v1.25.0)
  - Upgrading symfony/polyfill-intl-normalizer (v1.24.0 => v1.25.0)
  - Upgrading symfony/polyfill-mbstring (v1.24.0 => v1.25.0)
  - Upgrading symfony/polyfill-php80 (v1.24.0 => v1.25.0)
  - Upgrading symfony/process (v6.0.3 => v6.0.5)

Let's feed that to TestBot to see if anything/what breaks.

Well that went better than expected!

Seems like besides some side-stepping of our min-stability testing for using a dev release, we are good with Composer 2.3.x if nothing major changes.

I think we only need to wait until the official release is out, change "composer/composer": "^2.2.4", to "composer/composer": "^2.3.0", in composer.json and "symfony/console": "^5.4", to "symfony/console": "^6.0", in core/composer.json and do a composer update composer/composer -W afterwards.

Also creating a follow-up for the Remaining tasks bit seems in order, if not done already:

See if PSR/log 3 compatibility is possible after the update, and add forward to compatibility to core for its changes.

Besides the random testfailure in Drupal\Tests\layout_builder\FunctionalJavascript\BlockFormMessagesTest::testValidationMessage that is plaguing all core tests at the time this testrun was done, it seems that using composer/composer 2.3.0-RC1 and "symfony/console": "^6.0" is working out fine.

The only thing remaining to do is restoring the MINIMUN_STABILITY back to stable in core/tests/Drupal/BuildTests/Composer/Template/ComposerProjectTemplatesTest.php which is currently set to RC whenever the official composer 2.3.0 is released.

Not saying we _need_ to look at/commit this now, but that we _can_.

Thanks for keeping this up to date - this is looking promising indeed.

Looking at Composer's release history there has historically been less than two weeks (and sometimes only even one day!) between RC and final, so we can probably wait for 2.3.0.

Thanks @longwave, I agree.

Postponing on the official Composer 2.3.0 release.

Unpostponing since https://github.com/composer/composer/releases/tag/2.3.0 landed

Dependency updates only, no code changes were required, therefore RTBC.

$ composer-lock-diff --no-links
+----------------------------------+---------+---------+
| Production Changes               | From    | To      |
+----------------------------------+---------+---------+
| composer/semver                  | 3.2.9   | 3.3.1   |
| symfony/console                  | v5.4.3  | v6.0.5  |
| symfony/polyfill-ctype           | v1.24.0 | v1.25.0 |
| symfony/polyfill-intl-grapheme   | v1.24.0 | v1.25.0 |
| symfony/polyfill-intl-normalizer | v1.24.0 | v1.25.0 |
| symfony/polyfill-mbstring        | v1.24.0 | v1.25.0 |
| symfony/polyfill-php80           | v1.24.0 | v1.25.0 |
| symfony/process                  | v6.0.3  | v6.0.5  |
+----------------------------------+---------+---------+

+-------------------------+--------+--------+
| Dev Changes             | From   | To     |
+-------------------------+--------+--------+
| composer/composer       | 2.2.6  | 2.3.0  |
| composer/pcre           | 1.0.1  | 3.0.0  |
| composer/xdebug-handler | 2.0.4  | 3.0.3  |
| symfony/filesystem      | v6.0.3 | v6.0.6 |
+-------------------------+--------+--------+

Might need CR and release notes?

I've tagged this issue in the CR https://www.drupal.org/node/3265441

We should open a follow-up to see if psr/log v3 is supportable now.

Committed 1b79d50 and pushed to 10.0.x. Thanks!

Thanks @alexpott, created #3272447: Update to PSR/log v3 as a follow-up

For dep updates, we always want release notes, but almost never need a CR unless there is also an API change in Drupal APIs because of it. :)

There's bugfixed version released
https://github.com/composer/composer/releases/tag/2.3.2