Handle test traits in DataProviderAnnotationToAttributeRector

[TomasVotruba]

@dataProvider annotations inside test traits were never converted, because TestsNodeAnalyzer::isInTestClass() only checks $classReflection->is(TestCase::class). A trait has no parent, so that check can never match — the whole file is skipped.

Real-world case in Mautic:

namespace Mautic\CoreBundle\Tests\Twig;

trait TwigIntegrationTestTrait
{
    public static function integrationTestDataProvider(): iterable
    {
        return static::getIntegrationTestData();
    }

    /**
     * @dataProvider integrationTestDataProvider
     */
    public function testIntegration($file, $message): void
    {
        // ...
    }
}

Left untouched by the PHPUnit 10 set, so the upgrade silently misses it.

Change

Traits are now detected by a Test/Tests namespace part, since test traits live next to the test cases that use them:

+        // traits have no parent, so the test case check below can never match them;
+        // fall back to the namespace, as test traits live next to the test cases that use them
+        if ($classReflection->isTrait()) {
+            return $this->isInTestsNamespace($classReflection);
+        }
+
         return array_any(
             PHPUnitClassName::TEST_CLASSES,
             fn (string $testCaseObjectClass): bool => $classReflection->is($testCaseObjectClass)
         );

DataProviderAnnotationToAttributeRector also carried its own ! $classReflection->isClass() guard, which blocked traits even once the analyzer accepted them. Dropped — isInTestClass() already rejects interfaces and enums, so the guard was redundant.

Result:

 trait SomeTestTrait
 {
-    /**
-     * @dataProvider someMethod()
-     */
+    #[\PHPUnit\Framework\Attributes\DataProvider('someMethod')]
     public function test(): void
     {
     }
 }

Note

isInTestClass() is used by ~74 rules, so this widens all of them to test traits — which is the intended behaviour, but worth a second look.