fix: unbound breakpoints in sourcemaps on Chrome 112

[connor4312]

Chrome Dev (112) no longer has any stackframes for instrumentation
breakpoints, which was resulting in a thrown error.

Fixes #1567

[joj]

@connor4312 does this mean that any old version of VS and VSCode will fail with newer versions of Chrome? Should we let people in Chromium know about this? This feels like something that has the potential of breaking every IDE that supports CDP, not just ours :)

[connor4312]

does this mean that any old version of VS and VSCode will fail with newer versions of Chrome

Yes. It would break any client who uses instrumentation breakpoints and assumes (without checking) that there is at least one call frame on every pause event. I don't know how widely used this pattern is, but I sent a mail to someone on their team whom I've talked to recently regarding instrumentation pauses.

[connor4312]

Fyi, Chrome has rolled this back in 112 https://bugs.chromium.org/p/chromium/issues/detail?id=1421661