LLDB: add basic Wasm e2e test with WasmKit

[MaxDesiatov]

A follow up PR on swiftlang/swift will run this test after WasmKit is built. In the meantime, this test can be invoked manually from swiftlang repositories checkout, for example this way on macOS for a --release-debuginfo build:

BDIR=$PWD/build/buildbot_osx
  PYTHONPATH=$BDIR/lldb-macosx-arm64/bin/LLDB.framework/Resources/Python \
  DYLD_FRAMEWORK_PATH=$BDIR/lldb-macosx-arm64/bin \
  /tmp/lldb-test-venv/bin/python3.13 llvm-project/lldb/test/API/dotest.py \
    --executable $BDIR/lldb-macosx-arm64/bin/lldb \
    --cmake-build-type RelWithDebInfo \
    --llvm-tools-dir $BDIR/llvm-macosx-arm64/bin \
    --env LLVM_TOOLS_DIR=$BDIR/llvm-macosx-arm64/bin \
    --env WASMKIT=$BDIR/wasmkit-macosx-arm64/bin/wasmkit \
    --env WASI_SYSROOT=$BDIR/wasi-sysroot/wasm32-wasip1/sysroot \
    --env WASI_RESOURCE_DIR=$BDIR/wasi-sysroot/wasm32-wasip1/resource-dir \
    -p TestWasmE2E llvm-project/lldb/test/API/functionalities/wasm-e2e/

[MaxDesiatov]

@swift-ci test

[felipepiovezan]

Jonas is probably a better person to comment here, but the one thing that sticks out to me is that this test takes a different approach to compiling the code. Is it not possible to use the usual Makefile approach? This pushes all the test suite configuration steps (environment variables, etc) to the build stage (of lldb itself)