Sema: Fix crash in type resolution when tuple type contains type variables

This can happen when we're generating constraints and resolving the
type annotations written in a closure expression. Just skip the
non-copyable check in this case.

Fixes rdar://problem/143031466.

Author: slavapestov

lib/Sema/TypeCheckType.cpp

@@ -5676,6 +5676,7 @@ NeverNullType TypeResolver::resolveTupleType(TupleTypeRepr *repr,
         inStage(TypeResolutionStage::Interface) &&
         !moveOnlyElementIndex.has_value() &&
         !ty->hasUnboundGenericType() &&
+        !ty->hasTypeVariable() &&
         !isa<TupleTypeRepr>(tyR)) {
       auto contextTy = GenericEnvironment::mapTypeIntoContext(
           resolution.getGenericSignature().getGenericEnvironment(), ty);

test/Constraints/issue-77315.swift

@@ -0,0 +1,5 @@
+// RUN: %target-typecheck-verify-swift
+
+func foo<T>(_: () -> (Optional<T>, Int)) -> T { fatalError() }
+
+let x: Int = foo { () -> (Optional, Int) in fatalError() }