[ConstraintSystem] Fix a misleading argument mismatch error when using wrapped parameters.

[hborla]

When calling a function with a wrapped parameter, the solver will produce a misleading error message if the argument type isn't convertible to the parameter type:

import SwiftUI

func messageView(@Binding message: String) -> some View { // error: Property type 'Binding<String>' does not match 'wrappedValue' type 'String'
  EmptyView()
}

struct S {
  @Binding var message: String

  func test() {
    messageView(message: $message) // the actual error is that Binding<String> was passed here
  }
}

This happens because when type checking the function call, the solver will generate constraints for the property wrapper attribute chain, which will equate each wrapped-value type of a wrapper attribute with the next property wrapper attribute type (or the property type itself, if it's the innermost wrapper attribute).

For regular function parameters, these constraints were already generated and solved for when type checking the parameter declaration anyway, and they don't need to be repeated for function calls. This only needs to be done for closure parameters, so the fix is to only call generateWrappedPropertyTypeConstraints when resolving closures.

Resolves: SR-15030

[hborla]

@swift-ci please smoke test