Get deprecations showing on gitlab 'next core version' test

The first step is to undo the recent fix, so that gitlab has something to show.

There is relevant discussion on #3400979: Is SYMFONY_DEPRECATIONS_HELPER: weak correct for contrib deprecation testing needs? →

Took a while to get there but we now have a failing test at 10.2 for the deprecation error
https://git.drupalcode.org/issue/module_filter-3414272/-/jobs/623167

Now fix the error and it should be green.

I have also added a test at next_minor (which is currently 10.2.x but will become 10.3.x when that branch is created) and next_major (which is 11.x).

Rebuilt the branch locally, as the gitlab UI 'rebase' button is no longer available. The "resolve conflicts" button added the latest commits into this branch, and made the 'changes' confusing. So I trashed the branch, re-created locally and force-pushed. It is now a clean MR again.

That's good, as we can see that the "next minor" phpunit job reports the deprecation.
https://git.drupalcode.org/issue/module_filter-3414272/-/jobs/658013#L112

   Remaining self deprecation notices (1)
      1x: Passing null to the $typedConfigManager parameter of
    ConfigFormBase::__construct() is deprecated in drupal:10.2.0 and must be an
    instance of \Drupal\Core\Config\TypedConfigManagerInterface in
    drupal:11.0.0. See https://www.drupal.org/node/3404140
        1x in ModuleFilterSettingsFormTest::testModuleFilterSettingsForm from
    Drupal\Tests\module_filter\Kernel\Form

I have set this job to have 'allow_ failure:false' so that the pipeline ends amber not red. That is enough to alert us of deprecations that we can then fix.

Now that I have removed the forced deprecation, the latest pipeline is all green
https://git.drupalcode.org/issue/module_filter-3414272/-/pipelines/79754

But the previous pipeline shows the amber warning for 'next minor' when the deprecation was not fixed
https://git.drupalcode.org/issue/module_filter-3414272/-/pipelines/79460

Currently 'phpunit next minor' is running core 10.2.3-dev which is the same as the plain 'phpunit' job. But the Gitlab Templates project maintains this setting and when 10.3.x-dev is created this will be used in the 'next minor' job. So we do not need to do anything, the core version will automatically test the newer realese when it is available.

Ready for review!

Relying on your expertise on gitlab for this one.

Thanks for the commit (and the confidence)
:-)

Automatically closed - issue fixed for 2 weeks with no activity.