Do not perform deep validity check of jmethodid on JDK 26+

[jbachorik]

What does this PR do?:
Fix completely dysfunctional Java frame symbolication on Java 26

Motivation:
https://bugs.openjdk.org/browse/JDK-8268406 changed how jmethodid was represented in Hotspot JVMs.
Although the original fix for this was provided with async-profiler, another, sneakier issue remained in DD Java profiler - we perform deep validation of jmethodid to avoid surprising crashes due to attempts to access an invalid memory.
However, this validation is completely wrong on JDK 26 and later because jmethodids are now just a monotonically increasing key to a side table and we can not really validate anything.

Additional Notes:

How to test the change?:
Run a test load, capture profile and check the stacktraces. There should be no 'jvmtiError' frames.

For Datadog employees:

• If this PR touches code that signs or publishes builds or packages, or handles
  credentials of any kind, I've requested a review from @DataDog/security-design-and-guidance.
• This PR doesn't touch any of that.
• JIRA: PROF-14087

Unsure? Have a question? Request a review!

[dd-octo-sts]

CI Test Results

Run: #23361687570 | Commit: 4a6bff8 | Duration: 10m 21s (longest job)

✅ All 32 test jobs passed

Status Overview

JDK	glibc-aarch64/debug	glibc-amd64/debug	musl-aarch64/debug	musl-amd64/debug
8	-	✅	-	-
8-ibm	-	✅	-	-
8-j9	✅	✅	-	-
8-librca	-	-	✅	✅
8-orcl	-	✅	-	-
11	-	✅	-	-
11-j9	✅	✅	-	-
11-librca	-	-	✅	✅
17	✅	✅	-	-
17-graal	✅	✅	-	-
17-j9	✅	✅	-	-
17-librca	-	-	✅	✅
21	✅	✅	-	-
21-graal	✅	✅	-	-
21-librca	-	-	✅	✅
25	✅	✅	-	-
25-graal	✅	✅	-	-
25-librca	-	-	✅	✅

Legend: ✅ passed | ❌ failed | ⚪ skipped | 🚫 cancelled

Summary: Total: 32 | Passed: 32 | Failed: 0

---

Updated: 2026-03-20 20:53:34 UTC

[zhengyu123]

LGTM