TTD - Script file location for VSCode during debugging

If record and replay happen on different machines the location of the source code may change. However, when we replay our code we give VSCode the original URI for the source, which may not exist on the local machine, during the source load event. This can cause issues if VSCode attempts to access the file URI. As a temporary solution we need to give VSCode the location where the code is actually stored.

No files or tests are named. Start by tracing the source load event during time-travel replay and how the debugger supplies the source URI to VSCode. Done means replay supplies the source's actual local location instead of the original recorded URI, with the debugging behavior verified across different machines.

Written by the indexing model from the issue text.