Putting breakpoints in files outside of a Python SAM App causes "pydev debugger: warning: trying to add breakpoint to file that does not exist"

[awschristou]

If you debug a Python SAM App, but have breakpoints set on other applications/code within your VS Code workspace folder that isn't in the scope (CodeUri) of the App being debugged, warnings like this appear in the output:

Waiting for debugger to attach...
pydev debugger: warning: trying to add breakpoint to file that does not exist: /var/task/C:/code/sam-apps/js-app/hello-world/app.js (will have no effect)
pydev debugger: warning: trying to add breakpoint to file that does not exist: /var/task/C:/code/sam-apps/other-py-app/hello_world/app.py (will have no effect)
...debugger attached

We should try to create a "clean" debugging experience for the lambda function that is being debugged locally, without impacting any of the user's other settings (like removing breakpoints)

Acceptance Criteria:

• no warnings about other breakpoints
• user doesn't lose any other breakpoints they may have set

[awschristou]

Something we might be able to do:

• detect when debug sessions start (vscode.debug.onDidStartDebugSession / onDidChangeActiveDebugSession / ...)
• if debug session is a python session that was started by the toolkit, iterate the current breakpoints (vscode.debug.breakpoints)
  • for each breakpoint not relevant to the codeuri location of the debug session,
    • remove breakpoint (vscode.debug.removeBreakpoints)
    • re-add the breakpoints, but in a disabled state (vscode.debug.addBreakpoints)
    • store the breakpoints somewhere (global/workspace state)
• detect when debug session ends (onDidTerminateDebugSession / onDidChangeActiveDebugSession)
• restore the disabled breakpoints from global state

[justinmk3]

confirmed in 1.12