RFR: 8257197: Add additional verification code to PhaseCCP

[Emanuel Peter]

**Targetted for JDK-21.**

We have had many bugs that could be tracked back to missing optimizations during PhaseCCP.
Often the problem is that a node `x` has an input (of input of input) `y` which is modified, but `y` does not notify `x` (does not push it to the worklist). For one this is a missed opportunity to optimize, but it can also lead to failed assumptions later: often we assume that all that can be optimize is already optimized.
This verification helps us debug faster, and can also help when `Value` optimizations suddenly do further-reaching traversals, which would require further-reaching notifications.

Sadly, the verification is not total: we have some exceptions. Especially for `LoadNode`, which perform a walk up the memory inputs, which can go arbitrarily far, to look for relates `StoreNode`s. Notification would thus have to put very many nodes on the worklist. The question is if the potential additional optimization is worth the compile-time. If we decided yes, then one we might want to implement a listener-style notification: when a node visits inputs during `Value`, it could subscribe to all (or the relevant) visited input-nodes for future updates. Currently, we just mostly do fixed 1-hop or 2-hop notification of output nodes.

FYI: I plan to do a similar verification, and a refactoring of `PhaseCCP::push_child_nodes_to_worklist` and `PhaseIterGVN::add_users_to_worklist` in [JDK-8298094](https://bugs.openjdk.org/browse/JDK-8298094).

-------------

Commit messages:
 - 8257197: Add additional verification code to PhaseCCP

Changes: https://git.openjdk.org/jdk/pull/11529/files
 Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=11529&range=00
  Issue: https://bugs.openjdk.org/browse/JDK-8257197
  Stats: 54 lines in 2 files changed: 54 ins; 0 del; 0 mod
  Patch: https://git.openjdk.org/jdk/pull/11529.diff
  Fetch: git fetch https://git.openjdk.org/jdk pull/11529/head:pull/11529

PR: https://git.openjdk.org/jdk/pull/11529