Fixes #17765

The offender for this crash appears to be this snippet:

This branch triggers when applying type args to a type that is generic with respect to a single ParamSpec. It allows double brackets to be omitted when providing a parameter specification by wrapping all of the provided type arguments into a single parameter specification argument (i.e. equating Foo[int, int] to Foo[[int, int]]). This wrapping occurs unless:

• there is only a single type argument, and it resolves to Any (e.g. Foo[Any])
• there is only a single type argument, and it's a bracketed parameter specification or a ParamSpec (e.g. Foo[[int, int]])

The problem occurs when multiple type arguments provided and at least one of them is a bracketed parameter specification, as in Foo[[int, int], str].

Per the rules above, since there is more than 1 type argument, mypy attempts to wrap the arguments into a single parameter specification. This results in the attempted creation of a Parameters instance that contains another Parameters instance, which triggers this assert inside Parameters.__init__:

I think a reasonable solution is to forgo wrapping the type arguments into a single Parameters if any of the provided type arguments are a Parameters/ParamSpecType. That is, don't transform Foo[A1, A2, ...] to Foo[[A1, A2, ...]] if any of A1, A2, ... are a parameter specification.

This change brings the crash case inline with mypy's current behavior for a similar case:

# Current behavior
P = ParamSpec("P")
class C(Generic[P]): ...
c: C[int, [int, str], str]  # E: Nested parameter specifications are not allowed

Before this change:

P = ParamSpec("P")
class C(Generic[P]): ...
class D(C[int, [int, str], str]): ... # !!! CRASH !!!

After this change:

P = ParamSpec("P")
class C(Generic[P]): ...
class D(C[int, [int, str], str]): ... # E: Nested parameter specifications are not allowed