[turbofan] Properly respect --max_inlining_levels with Ignition.

The logic to test whether we already reached --max_inlining_levels
when inlining into some optimized function only checked specifically
for FrameStateType::kJavaScriptFunction, and thereby didn't properly
account for FrameStateType::kInterpretedFunction, which is what we
see when we come in via the bytecode pipeline.

Review-Url: https://codereview.chromium.org/2329923002
Cr-Commit-Position: refs/heads/master@{#39328}

src/compiler/js-inlining-heuristic.cc

@@ -109,7 +109,7 @@ Reduction JSInliningHeuristic::Reduce(Node* node) {
        frame_state->opcode() == IrOpcode::kFrameState;
        frame_state = NodeProperties::GetFrameStateInput(frame_state)) {
     FrameStateInfo const& frame_info = OpParameter<FrameStateInfo>(frame_state);
-    if (frame_info.type() == FrameStateType::kJavaScriptFunction) {
+    if (FrameStateFunctionInfo::IsJSFunctionType(frame_info.type())) {
       if (++level > FLAG_max_inlining_levels) {
         TRACE(
             "Not considering call site #%d:%s, because inlining depth "