fix(dead-code): preserve generic @return tags in `RemoveReturnTagIn…

[maartenpaauw]

This fixes RemoveReturnTagIncompatibleWithNativeTypeRector incorrectly stripping @return self<T> and @return ClassName<T> docblocks when the native return type is self.

Problem

Given a templated class:

/**
 * @template TAdded
 * @template TRemoved
 */
final readonly class Changes
{
    /**
     * @param list<TAdded> $added
     * @param list<TRemoved> $removed
     */
    private function __construct(
        public array $added,
        public array $removed,
    ) {
    }

    /**
     * @param list<TAdded> $added
     * @param list<TRemoved> $removed
     *
     * @return self<TAdded, TRemoved>
     */
    public static function create(array $added, array $removed): self
    {
        return new self($added, $removed);
    }
}

The rule would remove @return self<TAdded, TRemoved> because it considered it incompatible with the native self return type. However, the annotation is not redundant, because it narrows the return type with template parameters that PHP's native type system cannot express. PHPStan and Psalm rely on these annotations for generic type inference.

Fix

Added an early bail-out when $returnTagValueNode->type is an instance of GenericTypeNode. This catches all @return Foo<T>, @return self<T>, and @return static<T> patterns at the PHPDoc AST level before any expensive type resolution occurs.

[TomasVotruba]

Looks good 👌