RFR: 8309399: JVMTI spec needs to clarify when OPAQUE_FRAME is thrown for reasons other than a native method

[Serguei Spitsyn]

It was decided in a local discussion with Chris and Alan to update the JVMTI spec to make descriptions/clarifications of some `JVMTI_ERROR_OPAQUE_FRAME` cases more consistent.
This impacts the following JVMTI functions:
  - `PopFrame`
  - `NotifyFramePop`
  - `ForceEarlyReturn<Type>`

A related CSR is going to be filed for this spec update.

Testing:
 - it is N/A in general but mach5 tiers 1-3 will be run to be completely safe

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

Commit messages:
 - 8309399: JVMTI spec needs to clarify when OPAQUE_FRAME is thrown for reasons other than a native method

Changes: https://git.openjdk.org/jdk/pull/26111/files
  Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=26111&range=00
  Issue: https://bugs.openjdk.org/browse/JDK-8309399
  Stats: 41 lines in 1 file changed: 12 ins; 12 del; 17 mod
  Patch: https://git.openjdk.org/jdk/pull/26111.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/26111/head:pull/26111

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