launch with remote debugging does not hit existing breakpoints until deactivating/reactivating them

Environment (please complete the following information):

• OS (e.g., Windows 10): macOS 26.3
• Extension version (e.g., 1.2.3): 2.1.10

Describe the bug:

It's expected that the breakpoints are unbound as long as the remove debugging session with MS Edge is not running, I would expect that the breakpoints bound as soon as the remote debugging sessions is established.

This is not the case. They remain unbound after lauching the browser.
The breakpoints are bound as soon as I toggle activate/

Repro steps:

Launch Edge with devtools:

Navigate to the page that loads the src file, Home.controller.js in my example.

The breakpoints are did not bind:

I toggle breakpoints off/on:

Now without even reloading the web page, the breakpoints are bound:

Expected behavior:

To not have to manually toggle breakpoints before they are bound.

Additional context:

{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "node",
      "name": "cds watch",
      "request": "launch",
      "cwd": "${workspaceFolder}",
      "runtimeExecutable": "cds",
      "args": ["watch", "--with-mocks", "--in-memory?"],
      "skipFiles": ["<node_internals>/**"]
    },
    {
      "type": "pwa-msedge",
      "name": "Launch Microsoft Edge",
      "request": "launch",
      "runtimeArgs": ["--remote-debugging-port=9222"],
      "url": "http://localhost:4004",
      "webRoot": "${workspaceFolder}/app/cockpit/webapp",
      "presentation": {
        "hidden": true
      }
    },
    {
      "type": "vscode-edge-devtools.debug",
      "name": "Open Edge DevTools",
      "request": "attach",
      "url": "http://localhost:4004",
      "presentation": {
        "hidden": true
      }
    }
  ],
  "compounds": [
    {
      "name": "Launch Edge and attach DevTools",
      "configurations": ["Launch Microsoft Edge", "Open Edge DevTools"]
    }
  ]
}

Reproduce the compound "Launch Edge and attach DevTools" configuration with the provided macOS and Edge setup, then trace how breakpoints are handled when the remote debugging session is established. The fix is done when existing breakpoints bind automatically without manually deactivating and reactivating them; the issue names no source files or tests.