[Config] Add ruleWithConfigurationComposerVersionBound()

[TomasVotruba]

ComposerPackageConstraintInterface binds a whole rule to a package version. There is no way to bind a single configuration item - e.g. one AnnotationToAttribute pair - to the package version that introduced it.

This adds a version-bound variant of ruleWithConfiguration():

$rectorConfig->ruleWithConfigurationComposerVersionBound(
    AnnotationToAttributeRector::class,
    [new AnnotationToAttribute('test', 'PHPUnit\Framework\Attributes\Test')],
    'phpunit/phpunit',
    '>=10.0'
);

The configuration is registered only when the analysed project has a matching installed version. Since repeated ruleWithConfiguration() calls for the same rule class are merged, version-specific pairs stack on top of version-neutral ones across set files:

// version-neutral pairs
$rectorConfig->ruleWithConfiguration(AnnotationToAttributeRector::class, [
    new AnnotationToAttribute('someTag', SomeAttribute::class),
]);

// only on PHPUnit 11+
$rectorConfig->ruleWithConfigurationComposerVersionBound(
    AnnotationToAttributeRector::class,
    [new AnnotationToAttribute('someElevenTag', SomeElevenAttribute::class)],
    'phpunit/phpunit',
    '>=11.0'
);

Version resolving reuses InstalledPackageResolver, so it follows the same rules as ComposerPackageConstraintFilter, including the composer.json constraint priority added in #8242. An unresolvable version - package not installed - means the configuration is not registered, same as the existing filter.

[TomasVotruba]

Ref #7877