Lines that generate multiple breakpoints cause the UI to visually drop later breakpoints

In the case of lines with:
- multiple statements
- generated functors

When a line breakpoint is set on them, the UI does not expect additional breakpoints to be generated. The DAP will ask for the breakpoint details for each breakpoint created through the UI. The number of breakpoints that is returned must match the request in number and order.

There are two options:
- Keep an internal mapping of BPs for the debugger tracking all IDs associated with the breakpoints.
- Only allow a single breakpoint for each selected UI breakpoint
- This prohibits functor breakpoints unless we introduce Q# codegen, conditional breakpoints, or force users to manually define operation functor implementations

Start by tracing how the debugger handles DAP breakpoint requests for lines with multiple statements or generated functors. Compare the requested breakpoints with the returned number and order; done means later breakpoints no longer disappear from the UI, using one of the two approaches described in the issue.

Written by the indexing model from the issue text.