PPC/s390: [wasm] First plumbing for debugging in Liftoff

Port 7b79a02d

Original Commit Message:

    This CL adds a --debug-in-liftoff flag, which takes another path in
    {WasmScript::SetBreakPointForFunction}, and sets the breakpoint via
    {wasm::DebugInfo} (Liftoff-related) instead of {WasmDebugInfo} (C++
    interpreter related).
    Actual breakpoint support is not there yet, so the new test which sets
    this flag does not currently break anywhere. This will change with a
    future CL.

R=clemensb@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com
BUG=
LOG=N

Change-Id: I632e4c945c88f58d8caba8688356f66406bc04aa
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2016915Reviewed-by: Clemens Backes <clemensb@chromium.org>
Commit-Queue: Milad Farazmand <miladfar@ca.ibm.com>
Cr-Commit-Position: refs/heads/master@{#65953}

test/inspector/inspector.status

@@ -71,6 +71,7 @@
 ['arch == ppc or arch == ppc64', {
   # Liftoff needs to be enabled before running these tests.
   'debugger/wasm-scope-info-liftoff': [SKIP],
+  'debugger/wasm-set-breakpoint-liftoff': [SKIP],
 }],  # 'arch == ppc or arch == ppc64'
 
 ##############################################################################
@@ -79,6 +80,7 @@
   'debugger/set-script-source-stack-padding': [SKIP],
   # Liftoff needs to be enabled before running these tests.
   'debugger/wasm-scope-info-liftoff': [SKIP],
+  'debugger/wasm-set-breakpoint-liftoff': [SKIP],
 }],  # 'arch == s390 or arch == s390x'
 
 ##############################################################################