[nojit] Check that --jitless is disabled when creating wasm code

Drive-by: Amend wasm test skips for lite mode.

Bug: v8:7777
Change-Id: I23e13b65e548c19d6b24a26e0b962a9978f54ed7
Reviewed-on: https://chromium-review.googlesource.com/c/1449616Reviewed-by: Michael Starzinger <mstarzinger@chromium.org>
Commit-Queue: Jakob Gruber <jgruber@chromium.org>
Cr-Commit-Position: refs/heads/master@{#59314}

src/wasm/wasm-code-manager.cc

@@ -445,6 +445,8 @@ WasmCode* NativeModule::AddOwnedCode(
     OwnedVector<const byte> reloc_info,
     OwnedVector<const byte> source_position_table, WasmCode::Kind kind,
     WasmCode::Tier tier) {
+  CHECK(!FLAG_jitless);  // TODO(jgruber): Support wasm in jitless mode.
+
   WasmCode* code;
   {
     // Both allocation and insertion in owned_code_ happen in the same critical

test/cctest/cctest.status

@@ -535,6 +535,7 @@
   'test-run-wasm-atomics64/*': [SKIP],
   'test-run-wasm-atomics/*': [SKIP],
   'test-run-wasm/*': [SKIP],
+  'test-run-wasm-exceptions/*': [SKIP],
   'test-run-wasm-interpreter/*': [SKIP],
   'test-run-wasm-js/*': [SKIP],
   'test-run-wasm-module/*': [SKIP],