Add CT helper to check for ChangesCurrentThread annotation

[nbhuiyan]

This is required for implementing the JIT inlining behaviour expected for the methods annotated by @ChangesCurrentThread.

Issue: #17519

[nbhuiyan]

@tajila I'd appreciate your review.

[tajila]

Is the result of that call going to be cached? You dont want to call this repeatedly since it needs to parse the method attributes

[nbhuiyan]

The result of the call would not get cached as there will be no more than one call per method being considered for inlining during a compilation, similar to @ForceInline and @DontInline which also dictate inlining behaviour. Caching is also not done for any of the other annotation helpers.

[tajila]

jenkins compile win jdk8

[tajila]

jenkins test sanity alinux64 jdk21

[0xdaryl]

Minor nit, maybe a question for @tajila.

Should this be >= 21 since JDK 20 is no longer available and we no longer build it? Or do we specify it this way because that's when the annotation was first introduced and its good for bookkeeping purposes? I'm fine either way, just curious.

[0xdaryl]

Actually, the annotation appears in JDK 19 as well it seems. So if we're back-leveling the JDKs for bookkeeping purposes then it should be at least JDK 19.

[tajila]

For new code, we typically don't account for out-of-support releases. So we can ignore jdk19 and jdk20.

[nbhuiyan]

I changed the JAVA_SPEC_VERSION check to 21. Once the tests you launched pass, I can squash and rebase.

[tajila]

jenkins test sanity alinux64 jdk21

[nbhuiyan]

The aarch64 test failure:

---TEST RESULTS---
Number of PASSED tests: 10 out of 11
Number of FAILED tests: 1 out of 11

---SUMMARY OF FAILED TESTS---
Check SSL Verbose Log for connection failure with Non SSL Server
-----------------------------

-----------------------------------
cmdLineTester_criu_jitserverPostRestore_1_FAILED

This is not related to the changes in this PR.

[tajila]

LGTM

@0xdaryl any concerns?