ci(deps-dev): Bump rector/rector from 2.6.3 to 2.6.5 in /vendor-bin/rector

[dependabot]

Bumps rector/rector from 2.6.3 to 2.6.5.

Release notes

Sourced from rector/rector's releases.

Released Rector 2.6.5

Caching

This release makes the cache smarter about config changes - fewer needless full re-runs, while still invalidating when results could actually differ.

Configured rule value changes now invalidate the cache (#8400)

withConfiguredRule() stored its config on the RectorConfig instance only, never in the cache hash. Changing a rule's values - same class, different config - kept serving the stale result.

 return RectorConfig::configure()
     ->withConfiguredRule(SomeRector::class, [
-        'old value',
+        'new value',
     ]);

Before: cache kept, files re-analysed with stale value. After: cache dropped, re-analysed with new value. Merged config now flows through a RULE_CONFIGURATIONS parameter into the strict cache hash. Upgrading invalidates the cache once for projects using configured rules.

--only <Rule> reuses the full-run cache (#8400)

Each --only selection has its own cache namespace, so a file left clean by a prior full run was re-analysed under --only even when nothing changed. A scoped run now falls back to the full-run cache (read only, file content still compared, so real edits are still picked up).

vendor/bin/rector process       # full run, files left clean are cached
vendor/bin/rector process --only "Rector\..\SomeRector"

Before: --only re-analyses every file. After: skips files the full run already left clean.

Directional cache invalidation on config change (#8397)

Previously any change to any config parameter dropped the whole cache. Now changes are compared by direction:

• removing a rule/set, or adding a skip -> strictly less work -> cache kept
• adding a rule/set, or removing a skip -> more work possible -> cache dropped
• output-affecting params (php version, import names, indent) -> any change still drops the cache
• runtime/reporting params (--parallel, memory limit, deprecation notices) -> never invalidate

 return RectorConfig::configure()
     ->withRules([
         SomeRector::class,
-        OtherRector::class,     // removing a rule -> cache kept
     ]);

 return RectorConfig::configure()
     ->withSkip([
</tr></table> 

... (truncated)

Commits

• f868660 Rector 2.6.5
• 1312741 Updated Rector to commit ffe4c3299281281135b533a839392ae34a4bfcfe
• 54cd3eb Updated Rector to commit 85e562c607f770f4f448f3116350e998c44cb370
• 1313cee Updated Rector to commit 13cbd813cd56168e1fc7a713f92227062cc4b943
• 9e25013 Updated Rector to commit 3bac42eb97293437491ee5e22d51b3cee8609455
• 04130f7 Updated Rector to commit cc5d6f984ffddd44fd000860acb21c2245f3b52e
• a7f993e Updated Rector to commit cc5d6f984ffddd44fd000860acb21c2245f3b52e
• 1d2fed1 Updated Rector to commit bfee018eaa8fc099d116fb8825abb94a354501d8
• 2e1ec84 Updated Rector to commit e6c36be32b8dda0178e62e06bc54ae3eccbe7d78
• eebf5b3 Updated Rector to commit d28960e60ac022ccdb6b9b461645881f21ed3bf9
• 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)