[wasm] Don't put TailCall nodes in the effect chain

TailCalls have no output effect, similarly to e.g. return nodes. Thus,
don't put them in the effect chain.
The current graph verifier does not complain about this, but once we
switch to the GraphAssembler, we will hit a SLOW_DCHECK there because
we are trying to use a node as effect which has no effect output.

R=jkummerow@chromium.org

Bug: v8:10070
Change-Id: I23d9516eb9bd42a5aca46b09ca74830eafce635c
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2017474
Commit-Queue: Clemens Backes <clemensb@chromium.org>
Reviewed-by: Jakob Kummerow <jkummerow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#65973}

src/compiler/wasm-compiler.cc

@@ -2621,8 +2621,9 @@ Node* WasmGraphBuilder::BuildCallNode(wasm::FunctionSig* sig,
   inputs[params + 2] = Effect();
   inputs[params + 3] = Control();
 
-  Node* call =
-      SetEffect(graph()->NewNode(op, static_cast<int>(count), inputs.begin()));
+  Node* call = graph()->NewNode(op, static_cast<int>(count), inputs.begin());
+  // Return calls have no effect output. Other calls are the new effect node.
+  if (op->EffectOutputCount() > 0) SetEffect(call);
   DCHECK(position == wasm::kNoCodePosition || position > 0);
   if (position > 0) SetSourcePosition(call, position);