[BUG] Debugging does not work when specifying `additional_includes`

[bastbu]

Describe the bug

When using the Debug (f5) command in the prompt flow VS Code extension, it is possible to set breakpoints in Python nodes to debug them. When I specify an additional_includes folder, I lose the ability to debug the code.

How To Reproduce the bug Steps to reproduce the behavior, how frequent can you experience the bug:

1. Create a new flow (pf flow init --flow foo)
2. Specify a folder with additional_includes in the flow.dag.yaml
3. Try to click Debug (f5) and observe that break points are not hit

Expected behavior

Debugging should work consistently, no matter whether we specify additional_includes or not.

Running Information(please complete the following information):

• Promptflow Package Version: promptflow==1.5.0
• Operating System: WSL2
• Python 3.9.18

[brynn-code]

Hi @bastbu , thanks for reaching us, that's a known issue when additional includes specified, because we will copy the flow files with additional includes to a temp folder to ensure flow can run successfully.

[ouphi]

@brynn-code Do you have an estimate for when this issue will be resolved? The files being copied to a temporary folder is causing several complications during local development.