[docs]: document remote debugging

### URL/Location

https://docs.aws.amazon.com/durable-execution/testing/

### Describe What's Incorrect or Lacking

you can use the Lambda Remote debugging with VS Code with durable functions.

https://docs.aws.amazon.com/lambda/latest/dg/debugging.html

Since Durable Functions pin the specific version of the lambda function in executions, it should hit the same sandbox that the placement service created, assuming the subsequent invocation happens within the 10-15 minutes that the placement service keeps the sandbox alive. This means that subsequent invocations should get routed to the same sandbox and re-attach to the debugger.

1. When you do a remote debugging session for a lambda function, lambda will create a new version of the function for the debugging session.
2. On the lambda placement service, this will create a new sandbox specific to that version of the lambda function. The debugger will attach to this specific sandbox.
3. It's a best effort approach -- it heavily relies on the fact that it's a new version specific to the debugging session, and should only have 1 invocation for that given version.
4. there's another limit around debugging where if the function is frozen for 60 seconds, the debugging session itself will end. So if you have a case like context.wait(300) (5 minute wait), while the sandbox might still be warm, the debugger will detach because the function hasn't done anything for 60 seconds.

### Suggested Improvement

_No response_

### Additional Context

_No response_

Start with the documentation page at https://docs.aws.amazon.com/durable-execution/testing/ and compare it with the linked Lambda remote-debugging guide. Document how remote debugging interacts with durable function versions, sandbox reuse, the 10–15 minute lifetime, and the 60-second freeze limit. Done means the page clearly explains the setup and its best-effort limitations.

Written by the indexing model from the issue text.