[Sets] Move every per-version rule into the composer-based set

[TomasVotruba]

Follow-up to #757, which removed the three already-covered sets. This moves the remaining eight — PHPUnit 4.0 through 11.0 — into composer-based.php, so no ComposerTriggeredSet is left in this package.

Each rule now declares the PHPUnit version its target API is available from:

final class GetMockRector extends AbstractRector implements ComposerPackageConstraintInterface
{
    /**
     * createMock() was added in PHPUnit 5.4
     */
    public function provideComposerPackageConstraint(): ComposerPackageConstraint
    {
        return new ComposerPackageConstraint('phpunit/phpunit', '>=5.4');
    }

That is what makes one set enough. A project upgrading from PHPUnit 6 straight to 12 previously needed every version set in between; now a single set applies exactly the rules its installed version supports.

Version bonds

Grounded in the API that the rule produces:

rule	bond	why
GetMockRector, GetMockBuilderGetMockToCreateMockRector	>=5.4	createMock()
ExceptionAnnotationRector, DelegateExceptionArgumentsRector	>=5.2	expectException(), expectExceptionMessage()
SpecificAssertInternalTypeRector, SpecificAssertContainsRector, AssertEqualsParameterToSpecificMethodsTypeRector	>=7.5	assertIsArray(), assertStringContainsString(), assertEqualsWithDelta()
AssertRegExpRector	>=9.1	assertMatchesRegularExpression()
ExplicitPhpErrorApiRector	>=8.4 <10.0	the expectDeprecation() family, removed in 10.0
TestListenerToHooksRector	>=9.0 <10.0	the hook interfaces, removed in 10.0

The remaining rules keep the version of the set they came from, marked as such in their docblock (inherited from the PHPUnit 10.0 set). That never applies a rule below where its set already claimed it worked, and the bond can be tightened to an exact minor later.

Upper bounds and their tests

ExplicitPhpErrorApiRector and TestListenerToHooksRector target APIs PHPUnit 10 removed. Left open-ended they would rewrite code on PHPUnit 12 into methods that no longer exist, so both carry <10.0 — which then disables them under the PHPUnit 13 installed here. Their tests read the version from a stub instead:

protected function provideComposerJsonFilePath(): string
{
    return __DIR__ . '/config/composer.json';
}

Two things deliberately left out

PropertyExistsWithoutAssertRector is not registered in composer-based. It matches assertObjectHasProperty() — the exact method the >=10.1 rename already in this set produces — so the two rewrite each other's output. The conflict is not new (both sat in the phpunit100 set together), but I did not want to encode its outcome as expected test output. Worth a separate look; the rule keeps its bond and its set file registration.

Duplicate configuration was dropped rather than moved. The phpunit90 and phpunit100 renames of assertRegExp(), assertObjectHasAttribute(), setMethods() and the file/directory asserts are already in composer-based against PHPUnit\Framework\Assert, which TestCase extends. Same for phpunit80's MockObject class rename, already covered by the >=6.0 map.

Fixtures

Two composer-based fixtures gained an assertTrue(true). AddDoesNotPerformAssertionToNonAssertingTestRector is now part of the set and was adding #[DoesNotPerformAssertions] to their empty test methods, which had nothing to do with what those fixtures test.

Green locally: 652 tests, PHPStan, ECS and Rector clean.