composer: bump rector/rector from 2.5.8 to 2.6.0

[dependabot]

Bumps rector/rector from 2.5.8 to 2.6.0.

Release notes

Sourced from rector/rector's releases.

Released Rector 2.6.0

Composer-based sets - let Rector handle upgrade from composer.json 🥳

The main theme of this release: rules that turn themselves on based on the package versions you actually have installed.

Instead of picking a Symfony or PHPUnit set by version number and guessing what applies, register the composer-based set once. Every rule inside checks composer.json/installed.json and only runs if the installed package version matches its constraint.

use Rector\Config\RectorConfig;
return RectorConfig::configure()
->withComposerBased(
doctrine: true,
phpunit: true,
symfony: true,
twig: true,
);

We're working on full coverage. At the moment, PHPUnit and Symfony rules are already migrated to this approach. Not only rules, but also rule configuration can be bound to a package version:

$rectorConfig->ruleWithConfigurationComposerVersionBound(
    SomeRector::class,
    [...],
    'phpunit/phpunit',
    '>=11.0'
);

To see what is active and why, there is a new command:

vendor/bin/rector composer-based

 Composer package bound rules
 ------------------------------- ----------------- ---------- ----------- --------
  Rule                            Package           Requires   Installed   Active
 ------------------------------- ----------------- ---------- ----------- --------
  RemoveExpectAnyFromMockRector   phpunit/phpunit   >=11.0     11.5.2      yes
  RedirectToRouteRector           symfony/...       >=2.6      7.2.1       yes
 ------------------------------- ----------------- ---------- ----------- --------
! [NOTE] 2 of 2 composer package bound items are active
</tr></table>

... (truncated)

Commits

• 24ef17c Rector 2.6.0
• ab604d2 Updated Rector to commit c78280165eac6dde449d9e39274fe4aabcec5c9a
• ea10ff7 Updated Rector to commit b9753962856e0449e0907d9679800bc3660e4534
• 67df0f5 Updated Rector to commit dce07db9085dba0be987c28f338d12f451eaedbc
• a0b6c3d Updated Rector to commit ec55677b9d59df1a3c9f24c23db44baf0d9b52ef
• 6d12107 Updated Rector to commit e73b1821edfc763ad2c1ba13747c4c019e7aa62b
• c844de2 Updated Rector to commit e8816ca63c26f5ace65c9f56b065ed5730bfecc1
• 06d803e Updated Rector to commit 4f594bad8b3bf5c355df311ea3c2bd924b328289
• 972ec24 Updated Rector to commit 4f594bad8b3bf5c355df311ea3c2bd924b328289
• 0d900b2 Updated Rector to commit 0247338b1d6656b8e91bb7f38eb7016aa4e351fe
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)