conformance: change generics_typevartuple_args.py case

I don't think this case should error; a type checker can solve Ts
to something like (object,) or (int | str,). This is not all that
different from the first call to func4(), where the two calls with (0,)
and (1,) lead to Ts being solved to a common supertype.

Author: JelleZijlstra

conformance/tests/generics_typevartuple_args.py

@@ -21,7 +21,7 @@ class Env:
     ...
 
 
-def exec_le(path: str, *args: * tuple[*Ts, Env], env: Env | None = None) -> tuple[*Ts]:
+def exec_le(path: str, *args: *tuple[*Ts, Env], env: Env | None = None) -> tuple[*Ts]:
     raise NotImplementedError
 
 
@@ -39,7 +39,7 @@ def has_int_and_str(x: int, y: str):
 # > *args: int, which accepts zero or more values of type int.
 
 
-def func1(*args: * tuple[int, ...]) -> None:
+def func1(*args: *tuple[int, ...]) -> None:
     ...
 
 
@@ -48,7 +48,7 @@ def func1(*args: * tuple[int, ...]) -> None:
 func1(1, "2", 3)  # E
 
 
-def func2(*args: * tuple[int, *tuple[str, ...], str]) -> None:
+def func2(*args: *tuple[int, *tuple[str, ...], str]) -> None:
     ...
 
 
@@ -59,7 +59,7 @@ def func2(*args: * tuple[int, *tuple[str, ...], str]) -> None:
 func2("")  # E
 
 
-def func3(*args: * tuple[int, str]) -> None:
+def func3(*args: *tuple[int, str]) -> None:
     ...
 
 
@@ -72,8 +72,7 @@ def func4(*args: tuple[*Ts]):
 
 
 func4((0,), (1,))  # OK
-func4((0,), (1, 2))  # E
-func4((0,), ("1",))  # E
+func4((0,), (1, 2))  # E (length mismatch)
 
 
 # This is a syntax error, so leave it commented out.