Do not treat method templates resolved to their bound as unresolved - #6823

A @phpstan-assert is not reported as redundant when its type contains a method template inferred as mixed. Example from doctrine/orm#12513:

/**
 * @template TItem
 * @param TItem[] $parameter
 * @phpstan-assert list<TItem> $parameter
 */
private static function validateVariadicParameter(array $parameter): void
{
    if (array_is_list($parameter)) {
        return;
    }

    throw new \InvalidArgumentException();
}

/**
 * @no-named-arguments
 */
public function groupBy(string ...$groupBy): void
{
    self::validateVariadicParameter($groupBy); // reported
}

/**
 * @no-named-arguments
 */
public function select(mixed ...$select): void
{
    self::validateVariadicParameter($select); // not reported
}

$groupBy and $select are both lists because of @no-named-arguments, so the assertion is already satisfied in both cases. Only groupBy() is reported today.

Every template has a bound, mixed when no of is declared. For a class template, "resolved type equals bound" means the call did not specify it, so the template is unknown. For a method template, the type is inferred from the arguments: TItem resolved to mixed is a real answer that happens to equal the default bound. The old check treated both as unresolved.

The bound fallback now applies to class templates only (TemplateTypeScope::getFunctionName() === null). Method templates resolved to their bound are treated as resolved, so their assertion is applied and the already-satisfied report runs.

Class templates that are really unresolved are still skipped. The native mirror in turbo-ext/src/DefaultNarrowingHelper.cpp applies the same change, and regression tests are in tests/PHPStan/Rules/Comparison/data/no-named-arguments-assert.php.