fix(java): address reachability issues in native image compilation with version 22.2.0

[mpeddada1]

Reproducer: https://github.com/mpeddada1/graalvm22.2-reachability. There were some changes introduced in GraalVM 22.2 which enabled reachibility handlers to be run concurrently by default. However, concurrent reachability doesn't seem to register classes correctly for reflection, therefore resulting in an error that looks like this for gapic libraries:

JUnit Vintage:BaseBigtableTableAdminClientTest:undeleteTableTest
    MethodSource [className = 'com.google.cloud.bigtable.admin.v2.BaseBigtableTableAdminClientTest', methodName = 'undeleteTableTest', methodParameterTypes = '']
    => java.lang.RuntimeException: Generated message class "com.google.bigtable.admin.v2.Table" missing method "getName".
       com.google.protobuf.GeneratedMessageV3.getMethodOrDie(GeneratedMessageV3.java:1929)
       com.google.protobuf.GeneratedMessageV3.access$1000(GeneratedMessageV3.java:79)
       com.google.protobuf.GeneratedMessageV3$FieldAccessorTable$SingularFieldAccessor$ReflectionInvoker.<init>(GeneratedMessageV3.java:2260)
       com.google.protobuf.GeneratedMessageV3$FieldAccessorTable$SingularFieldAccessor.<init>(GeneratedMessageV3.java:2334)
       com.google.protobuf.GeneratedMessageV3$FieldAccessorTable$SingularStringFieldAccessor.<init>(GeneratedMessageV3.java:3012)
       [...]
     Caused by: java.lang.NoSuchMethodException: com.google.bigtable.admin.v2.Table.getName()
       java.lang.Class.getMethod(DynamicHub.java:2108)
       com.google.protobuf.GeneratedMessageV3.getMethodOrDie(GeneratedMessageV3.java:1926)
       [...]

This change disables the support until this is fixed upstream.
Note: The RunReachabilityHandlersConcurrently option was introduced with GraalVM 22.2 and is unavailable in version 22.1.0.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[fniephaus]

Is -H:-RunReachabilityHandlersConcurrently still needed for this library in GraalVM 22.3.0 or later? It's unfortunately causing other user-facing issues (see oracle/graal#5868 (comment)).

[mpeddada1]

Thank you for following up on this PR @fniephaus! Unfortunately, the issue persists even with GraalVM 22.3.0 and 22.3.1 being used (for reference: https://github.com/mpeddada1/graalvm22.2-reachability#does-this-sample-work-without-the-workaround-in-graalvm-2231-latest and related conversation). As mentioned in oracle/graal#5194, the issue started happening with GraalVM 22.2.0 when reachability handlers were made concurrent by default. We would really appreciate any insights/workarounds you may have to unblock this without having to disable the argument.

[fniephaus]

Thanks for checking. We're tracking oracle/graal#5194 internally and will follow up with more info soon.

[mpeddada1]

Sounds great, thank you!

[fniephaus]

We've pushed a fix a while ago and it's now available in the latest GraalVM release. Could you please check again if -H:-RunReachabilityHandlersConcurrently is still needed?