Class-scoped `type` statement that references outer-scoped `TypeVar`

I wonder if this decision has any implications for potential future enhancements to runtime access of type params, as was proposed in this topic. Although I can’t immediately think of a concrete issue this would cause.

But with the current status quo the type syntax and backport via TypeAliasType definitely seems fine to allow, since there’s no longer any ambiguity as to whether the type var is bound to the type alias itself or to the class.