[Bug]: Breakpoint changes inside Ballerina services are not reflected after starting a debug session

[NipunaRanasinghe]

Description

When debugging Ballerina services, modifications to breakpoints (adding/ removing) after the debug session has started are not captured.

This issue results in the debugger not responding to the updated breakpoints, leading to debugging inconsistencies.

Steps to Reproduce

import ballerina/http;
import ballerina/io;

service on new http:Listener(8080) {
    resource function get hello() returns string {
        io:println("Hello World");
        return "Hello, World!";
    }
}

1. Use the above code and add a breakpoint on the println line.
2. Once its hit, add another breakpoint on the return statement and continue to the next breakpoint.
3. The debugger will not stop at the new breakpoint

Affected Version(s)

2201.11.0-beta

OS, DB, other environment details and versions

No response

Related area

-> Debugger

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

[NipunaRanasinghe]

Seems to be a regression added with 56348e3

[NipunaRanasinghe]

Closing with #43739

[github-actions]

This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
      - Reason/Regression - The issue has introduced a regression.
      - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
      - Reason/Complex - Issue occurred due to complex scenario.
      - Reason/Invalid - Issue is invalid.
      - Reason/Other - None of the above cases.