[liftoff][debug] Switch scope-info test over

This enables the --debug-in-liftoff flag in the wasm-scope-info test.
The expected output slightly differs, because we get another breakpoint
at the end of the function body, which was actually missing before.

R=thibaudm@chromium.org

Bug: v8:10351
Change-Id: Ic2628b26591763cea17403f74fe0f6d935633e6d
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2120535Reviewed-by: Thibaud Michaud <thibaudm@chromium.org>
Commit-Queue: Clemens Backes <clemensb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#66859}

test/inspector/debugger/wasm-scope-info-expected.txt

@@ -331,6 +331,19 @@ at (anonymous) (0:17):
  - scope (global):
    -- skipped globals
 
+Paused:
+Script wasm://wasm/d374ef0a byte offset 60: Wasm opcode 0xb
+Scope:
+at call_func (0:60):
+ - scope (global):
+   globals: "global0": 15 (number)
+ - scope (local):
+   locals: "var0": 4 (number), "var1": 7.199999809265137 (number)
+   stack: 
+at (anonymous) (0:17):
+ - scope (global):
+   -- skipped globals
+
 Paused:
 instance.exports.main(4)#
 

test/inspector/debugger/wasm-scope-info.js

@@ -2,9 +2,7 @@
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
-// Disable Liftoff to get deterministic (non-existing) scope information for
-// compiled frames.
-// Flags: --no-liftoff
+// Flags: --debug-in-liftoff
 
 let {session, contextGroup, Protocol} = InspectorTest.start(
     'Test retrieving scope information when pausing in wasm functions');