[turbolizer] Solve bug where the node 0 was not being selected

In the schedule phase (and only in this phase!) the node 0 was not
being selected due to `!0` being true. We meant to be checking
against undefined rather than this.

Bug: v8:7327
Notry: true
Change-Id: Ie675979219868725b0e345065cec7a2a7091fda8
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3008215Reviewed-by: Nico Hartmann <nicohartmann@chromium.org>
Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#75585}

tools/turbolizer/src/selection.ts

@@ -21,7 +21,7 @@ export class MySelection {
 
   select(s: Iterable<any>, isSelected?: boolean) {
     for (const i of s) {
-      if (!i) continue;
+      if (i == undefined) continue;
       if (isSelected == undefined) {
         isSelected = !this.selection.has(this.stringKey(i));
       }