bug(vex): Trivy skips the rule if we check the same parent from different paths.

[DmitriyLewen]

Description

We fixed an issue where two (or more) dependencies could cyclically depend on each other, causing incorrect traversal and follow-up logic.
See #9465

flowchart LR
  A --> B
  B --> A

Loading

But there are cases where a leaf reach the same ancestor through multiple distinct paths: in such situations, we skip applying the parent-filtering rule for that already-visited ancestor (we’ve already evaluated it), so we do not filter the vulnerability.

flowchart LR
  A --> B
  B --> C
  C --> X

  A --> D
  D --> E
  E --> F
  F --> X

  D --> G
  G --> H
  H --> F

Loading

Discussed in #9754

[knqyf263]

In your diagram, could you explain in detail which one is the leaf, which one is the parent, which one is the root, and where the filtering occurs?