JIT: assert if we see schema mismatches with dynamic pgo data (#85898)
When the profile data comes from dynamic PGO, the spanning tree encoded in the
schema produced by an earlier tier should exactly match the spanning tree for
the current jit attempt, since the JIT and method IL are identical.
(This is not the case for static PGO; that schema may have come from a different
JIT and/or different version of IL).
Note in release modes we won't assert; instead, we will silently throw the PGO
data away.
Follow-on change to #85805 to catch more issues like #85799.