Fix LLDB test failures after latest dependency version updates.

After #1805, we're seeing test failures like the following in `debug::lldb::test_debug_dwarf_ptr`:

```
test debug::lldb::test_debug_dwarf_ptr ... FAILED

failures:

---- debug::lldb::test_debug_dwarf_ptr stdout ----
thread 'main' panicked at 'didn't pass check > (lldb) target create "/home/runner/work/wasmtime/wasmtime/target/debug/wasmtime"
> Current executable set to '/home/runner/work/wasmtime/wasmtime/target/debug/wasmtime' (x86_64).
> (lldb) settings set -- target.run-args "-g" "--opt-level" "0" "tests/all/debug/testsuite/reverse-str.wasm"
> (lldb) command source -s 0 '/tmp/.tmpmh81yA'
> Executing commands in '/tmp/.tmpmh81yA'.
> (lldb) b reverse-str.c:9
> Breakpoint 1: no locations (pending).
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Matched #0: \bBreakpoint 1: no locations \(pending\)
> WARNING: Unable to resolve breakpoint to any actual locations.
> (lldb) r
> 1 location added to breakpoint 1
> Process 14667 stopped
> * thread #1, name = 'wasmtime', stop reason = breakpoint 1.1
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
Matched #1: \bstop reason = breakpoint 1\.1\b
> frame #0: 0x00007ffff7fcf053 JIT(0x5555571bdd70)`reverse(s=(__ptr = 66562), len=13) at reverse-str.c:9:12
^~~~~~~~
Matched #2: \bframe \#0\b
^~~~~~~~~~~~~~~~~~
Matched #3: \breverse\(s=\(__ptr =
Missed #4: "Hello, world\."
>
> Process 14667 launched: '/home/runner/work/wasmtime/wasmtime/target/debug/wasmtime' (x86_64)
> (lldb) p __vmctx->set(),&*s
', tests/all/debug/lldb.rs:52:5
```

We suspect the version-bump of some dependency caused this, though we aren't yet sure why (and we cannot reproduce locally). We will disable the test for now but we need to investigate and re-enable.