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

[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 spec sections:
>   - `PopFrame`
>   - `NotifyFramePop`
>   - `ForceEarlyReturn<Type>`
>   - `GetLocal<Type>`
>   - `SetLocal<Type>`
>   - general description of the `JVMTI_ERROR_OPAQUE_FRAME` error code
>   
> 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

Serguei Spitsyn has updated the pull request incrementally with one additional commit since the last revision:

  review: corrected OPAQUE_FRAME clarification for NotifyFramePop function

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

Changes:
  - all: https://git.openjdk.org/jdk/pull/26111/files
  - new: https://git.openjdk.org/jdk/pull/26111/files/da3f20a8..4f1d4170

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jdk&pr=26111&range=04
 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=26111&range=03-04

  Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 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