[5.5][SILGen] Fix a miscompile when emitting the application of a wrapped parameter

[hborla]

Cherry-pick of #37301

• Explanation: Extending property wrappers to parameters added a new way to invoke property wrapper generator functions. When emitting a call to the generator function for wrapped parameters, SILGen passed down the SGFContext when emitting the r-value of the argument. This caused a miscompile when the argument was an address-only type (e.g. a resilient type), because the argument was incorrectly initialized in place using the context, which was meant for the result of the generator function. The caller ended up overwriting the initialization with the result of the generator function anyway, and the r-value of the argument was never emitted, which violated ownership rules. The solution is to simply not pass down the context when emitting the argument.

• Scope: The scope is limited to property wrappers on function and closure parameters.

• Risk: Low risk. SGFContext is just an optimization, so not including it will not impact the correctness of emitting an r-value.

• Testing: Added an automated test to ensure that the problematic case does not violate any ownership rules. Without this change, the added test trips up the SIL verifier with SIL verification failed: Found mutating or consuming use of an in_guaranteed parameter?!: !ImmutableAddressUseVerifier().isMutatingOrConsuming(fArg).

• Reviewer: @slavapestov

Resolves: rdar://77572130

[hborla]

@swift-ci please test