[Java] disable async compilation for graalvm (#1222)

* disable async compilation for graalvm

* add asyncCompilationEnabled disable option doc.

* lint code

docs/guide/graalvm_guide.md

@@ -24,6 +24,9 @@ Another benefit using fury is that you don't have to configure [reflection json]
 very tedious, cumbersome and inconvenient. When using fury, you just need to invoke 
 `io.fury.Fury.register(Class<?>, boolean)` for every type you want to serialize.
 
+Note that Fury `asyncCompilationEnabled` option will be disabled automatically for graalvm native image since graalvm 
+native image doesn't support JIT at the image run time.
+
 ## Not thread-safe Fury
 Example:
 ```java

java/fury-core/src/main/java/io/fury/config/FuryBuilder.java

@@ -26,6 +26,7 @@
 import io.fury.serializer.Serializer;
 import io.fury.serializer.TimeSerializers;
 import io.fury.serializer.collection.GuavaCollectionSerializers;
+import io.fury.util.GraalvmSupport;
 import io.fury.util.LoggerFactory;
 import io.fury.util.Platform;
 import java.util.Objects;
@@ -258,6 +259,9 @@ public FuryBuilder withCodegen(boolean codeGen) {
    * serialization first and switch to jit serialization after async serializer jit for a class \ is
    * finished.
    *
+   * <p>This option will be disabled automatically for graalvm native image since graalvm native
+   * image doesn't support JIT at the image run time.
+   *
    * @see Config#isAsyncCompilationEnabled()
    */
   public FuryBuilder withAsyncCompilation(boolean asyncCompilation) {
@@ -305,6 +309,10 @@ private void finish() {
     if (suppressClassRegistrationWarnings == null) {
       suppressClassRegistrationWarnings = !requireClassRegistration;
     }
+    if (GraalvmSupport.IN_GRAALVM_NATIVE_IMAGE && asyncCompilationEnabled) {
+      LOG.info("Use sync compilation for graalvm native image since it doesn't support JIT.");
+      asyncCompilationEnabled = false;
+    }
   }
 
   /**