AWS Toolkit Debug Payload Causes Invocation Error

### Issue: AWS Toolkit Debug Payload Causes Invocation Error

#### **Summary**
When using AWS Toolkit for VS Code, invoking a Lambda function with a payload loaded via "Load Debug Config" results in an error. However, manually entering the same payload and invoking the function works fine.

#### **Steps to Reproduce**
1. Open VS Code and select a Lambda function for local debugging.
2. Use "Load Debug Config" to load a predefined payload.
3. Invoke the Lambda function.
4. Observe that an error occurs (`ENOENT` with `rg.exe`).

Alternatively:
1. Open VS Code and select a Lambda function for local debugging.
2. Manually enter the same payload instead of using "Load Debug Config."
3. Invoke the Lambda function.
4. The function executes successfully without errors.

#### **Expected Behavior**
Lambda invocation should work correctly regardless of how the payload is provided.

#### **Actual Behavior**
Using "Load Debug Config" to load the payload results in an invocation error (`SamLaunchRequestError` with `ENOENT` on `rg.exe`). Manually entering the payload avoids this issue.

#### **Environment**
- **AWS Toolkit Version**: `3.62.0 or 3.60.0`
- **VS Code Version**: `1.100.2`
- **SAM CLI Version**: `1.128.0`
- **OS**: `windows 10 Version2009 19045.5854`

Please investigate if this is a known issue or provide guidance on how to resolve it.

Reproduce the failure on Windows using AWS Toolkit for VS Code, the listed SAM CLI and extension versions, and a payload loaded through "Load Debug Config"; compare it with the manually entered payload path. Trace the ENOENT/SamLaunchRequestError involving rg.exe and verify that Lambda invocation succeeds for both payload-entry methods.

Written by the indexing model from the issue text.