fix(custom-resources): Custom resource provider framework not passing ResponseURL to user function (#21065)

#20889 included a change that broke the custom resource framework by not including the necessary presigned URL. This includes the presigned URL, and fixes the issue. This PR does not include test changes because this is the runtime code.

Closes #21058

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

Author: comcalvi

packages/@aws-cdk/custom-resources/lib/provider-framework/runtime/framework.ts

@@ -105,9 +105,7 @@ async function invokeUserFunction<A extends { ResponseURL: '...' }>(functionArnE
   // automatically by the JavaScript SDK.
   const resp = await invokeFunction({
     FunctionName: functionArn,
-
-    // Strip 'ResponseURL' -- the downstream CR doesn't need it and can only log it by accident
-    Payload: JSON.stringify({ ...sanitizedPayload, ResponseURL: undefined }),
+    Payload: JSON.stringify(sanitizedPayload),
   });
 
   log('user function response:', resp, typeof(resp));