[debugger] handle paused state when there are 0 frames

Discussion started here: https://github.com/flutter/devtools/pull/2683#discussion_r572410011

We can get into a state where the app is paused but there are not frames. The original discussion started as a question of whether or not we should support stepping in this case. This question still stands, but sparks a larger question of how we can make this case actionable for our users? If there are neither scripts nor frames to show, what will the user experience be like as the user steps / resumes? If they did not manually pause the app, how will the user understand why the app is paused?

In the web case, the app can be paused in some JS or SDK code for which we don't have any frames (do we have scripts at this point @grouma?). Perhaps we could add some fake frame `JS` that at least communicates to the user that their app is paused in JS code, and then point them to Chrome DevTools for a better JS debugging experience.

@grouma @bkonyi for input on what the debugging workflow should look like in this case for both web and mobile connections.

Start by reading the discussion in PR #2683, then trace how DevTools represents paused states when no frames or scripts are available. The desired behavior for stepping, resuming, and explaining web versus mobile pauses still needs agreement; done means a decided, actionable user experience is implemented and covered by relevant tests.

Vom Indexierungsmodell aus dem Issue-Text verfasst.