RFR: 8330253: Skip verify_consistent_lock_order when deoptimizing from monitorenter bytecode.

[Axel Boldt-Christmas]

The verification added in [JDK-8329757](https://bugs.openjdk.org/browse/JDK-8329757) will not work then deoptimization occurs on a monitorenter bytecode. The locking may be in a transitional state. This patch will skip the verification when this occurs.

Currently have only seen this reproduce with JVMTI when deoptimization occurs while a java thread is waiting on a contended monitor. However this could potentially be triggered from a VM entry slow path, so simply checking `current_pending_monitor` could be flaky as well. So instead simply avoid verification.

Running JVMTI reproducer. Starting full testing soon.

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

Commit messages:
 - Skip verify when deoptimizing from monitorenter bytecode.

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

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