Store JITServer AOT methods if they are delayed

If the option -XX:+JITServerAOTCacheDelayMethodRelocation is in effect,
then we delay the relocation of received AOT methods by default. When
this is the case, we should also store these methods in the local SCC so
that they will be available to be relocated later.

Signed-off-by: Christian Despres <[email protected]>

runtime/compiler/control/JITClientCompilationThread.cpp

@@ -2969,7 +2969,12 @@ remoteCompilationEnd(J9VMThread *vmThread, TR::Compilation *comp, TR_ResolvedMet
          }
 #endif /* J9VM_INTERP_AOT_RUNTIME_SUPPORT */
 
-      if (!compInfo->getPersistentInfo()->getJITServerUseAOTCache() || shouldStoreRemoteAOTMethods)
+      // If we're not using the AOT cache, we still store by default. This avoids certain test failures in the short term.
+      // Also, if we've explicitly been requested by the user to delay method relocations then we need to store methods
+      // in the SCC to support that option.
+      if (comp->getPersistentInfo()->getJITServerAOTCacheDelayMethodRelocation() ||
+          !compInfo->getPersistentInfo()->getJITServerUseAOTCache() ||
+          shouldStoreRemoteAOTMethods)
          {
          J9ROMMethod *romMethod = comp->fej9()->getROMMethodFromRAMMethod(method);
          TR::CompilationInfo::storeAOTInSharedCache(