(custom-resources): exceptions are not surfaced in cloudformation, re-opened

### Describe the bug

Referencing https://github.com/aws/aws-cdk/issues/31472
I made a mistake and I actually am using the provider framework lambda, so the previous issue was improperly closed.

The doc says to
Specifically, to report success or failure, have your Lambda Function exit in the right way: return data for success, or throw an exception for failure.

When our lambda throws an exception, the details are not surfaced in the Cloudformation dashboard. Instead, it says a generic
Received response status [FAILED] from custom resource. Message returned: Error: Uncaught lambda exception,....

### Regression Issue

- [ ] Select this option if this issue appears to be a regression.

### Last Known Working CDK Version

_No response_

### Expected Behavior

I expect the Reason to be populated with the Exception message, something like
"Received response status FAILED from custom resource. Message returned: ." where the reason is lambda exception.

### Current Behavior

We are seeing a generic error

Received response status [FAILED] from custom resource. Message returned: Error: Uncaught lambda exception, execution stopped Logs: /aws/lambda/my-lambda-function at invokeUserFunction (/var/task/framework.js:2:6) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async onEvent (/var/task/framework.js:1:369) at async Runtime.handler (/var/task/cfn-response.js:1:1676) (RequestId: abcdef-ghij-1234-5678-333f1c96d6d3)

### Reproduction Steps

CDK code:

Creating the user lambda stack
```
const lambdaStackFunction = ...CreateMyCustomDotnetLambda(...);

const provider = new custom_resources.Provider(this, 'MyProvider', {
logRetention: aws_logs.RetentionDays.ONE_WEEK,
onEventHandler: lambdaStackFunction,
});

const frameworkFunc = provider.node.tryFindChild('framework-onEvent') as aws_lambda.Function;

this.exportValue(frameworkFunc.functionArn, {
name: 'FrameworkFunctionArn'
});
```

```
export class MyResource extends Construct {
constructor(scope: Construct, id: string) {
super(scope, id);

const crProps: CustomResourceProps = {
resourceType: 'Custom::resource',
serviceToken: Fn.importValue(
'FrameworkFunctionArn'
)
};
const resource = new CustomResource(this, 'custom', crProps);
}
}
```

Our dotnet Lambda code:

```
public async Task> OnEvent(
CustomResourceRequest request,
ILambdaContext context
)
{
throw new Exception("I want this reason to show up");
}
```

### Possible Solution

_No response_

### Additional Information/Context

_No response_

### CDK CLI Version

2.145.0

### Framework Version

_No response_

### Node.js Version

20

### OS

Mac

### Language

TypeScript

### Language Version

4.8.3

### Other information

The lambda is in net8.0

I can confirm that there are two lambdas created. Here are the logs from the framework lambda:
```
2024-09-23T20:58:54.582Z a8012ec6-aaaa-bbbb-cccc-c0dda733096a INFO [provider-framework] user function threw an error: Unhandled

2024-09-23T20:58:54.641Z a8012ec6-aaaa-bbbb-cccc-c0dda733096a INFO [provider-framework] submit response to cloudformation https://cloudformation-custom-resource-response-useast1.s3.amazonaws.com//arn%3Aaws%3Acloudformation...... {
"Status": "FAILED",
"Reason": "Error: Uncaught lambda exception, execution stopped\n\nLogs: /aws/lambda/my-user-lambda\n\n at invokeUserFunction (/var/task/framework.js:2:6)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async onEvent (/var/task/framework.js:1:369)\n at async Runtime.handler (/var/task/cfn-response.js:1:1676)",
"StackId": "arn:aws:cloudformation:....",
"RequestId": ".....",
"PhysicalResourceId": "......",
"LogicalResourceId": "....."
}

```

This same node error is what gets surfaced in my cloudformation console, even though my user lambda is in dotnet.
In the previous issue https://github.com/aws/aws-cdk/issues/31472
the comment said

>onEvent should handle exception when possible, however, if some unexpected exception is thrown, the provider framework should be able to capture that and gracefully callback cloudformation as resource fails to be created.

I would expect the framework function to capture the thrown exception from the user dotnet lambda gracefully, and return the exception to the cloudformation console.

Let me know if I should provide more details.

Start by tracing the provider framework's invokeUserFunction and cfn-response.js paths referenced in the logs, using the supplied TypeScript CDK reproduction with the .NET OnEvent handler. Verify that the exception message from the user Lambda is preserved in CloudFormation's Reason instead of the generic framework error.

Written by the indexing model from the issue text.