So that we can have situations like:

• 4.14.0 includes 4.13.18 and 4.13.19 in its update sources.
• We want to silently block 4.13.18 > 4.14.0.
• We want to declare an update risk for 4.13.19 > 4.14.0.

Currently that doesn't seem to be possible, and I need to drop 4.14.0's ConsoleImplicitlyEnabled to avoid having 4.14.0 leak into conditional-updates for 4.13.18: graph-data#4326.

Definition of done:

• Cincinnati should respect when we remove an edge from the graph even if we have a conditional risk for the same edge.
• Add a test to the pre-submit in Cincinnati-graph-data to catch it in the PR.