[IJ/AS plugin] Don't crash when ToolingModel method are not present

[BoD]

Description

Got this crash:

org.gradle.tooling.model.UnsupportedMethodException: Unsupported method: ServiceInfo.getEndpointUrl().
The version of Gradle you connect to does not support that method.
To resolve the problem you can change/upgrade the target version of Gradle you connect to.
Alternatively, you can ignore this exception and read other information from the model.
	at org.gradle.tooling.model.internal.Exceptions.unsupportedMethod(Exceptions.java:33)
	at org.gradle.tooling.internal.adapter.ProtocolToModelAdapter$InvocationHandlerImpl.invoke(ProtocolToModelAdapter.java:435)
	at jdk.proxy17/jdk.proxy17.$Proxy391.getEndpointUrl(Unknown Source)
	at com.apollographql.ijplugin.gradle.GradleToolingModelService.computeGraphQLProjectFiles$getGraphQLProjectFiles(GradleToolingModelService.kt:235)
	at com.apollographql.ijplugin.gradle.GradleToolingModelService.computeGraphQLProjectFiles(GradleToolingModelService.kt:244)
	at com.apollographql.ijplugin.gradle.GradleToolingModelService.access$computeGraphQLProjectFiles(GradleToolingModelService.kt:40)
	at com.apollographql.ijplugin.gradle.GradleToolingModelService$FetchToolingModelsTask.run(GradleToolingModelService.kt:187)
	at com.intellij.openapi.progress.impl.CoreProgressManager.startTask(CoreProgressManager.java:429)
	at com.intellij.openapi.progress.impl.ProgressManagerImpl.startTask(ProgressManagerImpl.java:114)
	at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcessWithProgressAsynchronously$6(CoreProgressManager.java:480)
	at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$3(ProgressRunner.java:252)
	at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:186)
	at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$executeProcessUnderProgress$13(CoreProgressManager.java:604)
	at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:679)
	at com.intellij.openapi.progress.impl.CoreProgressManager.computeUnderProgress(CoreProgressManager.java:635)
	at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:603)
	at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:60)
	at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:173)
	at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$4(ProgressRunner.java:252)
	at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1768)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:702)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:699)
	at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:699)
	at java.base/java.lang.Thread.run(Thread.java:833)

This should be swallowed with a log instead, as this can normally happen when the tooling model evolves.

[martinbonnin]

This should be swallowed with a log instead, as this can normally happen when the tooling model evolves.

Just making sure I understand here. Is this happening when the AKIJP version is not matching the AKGP version? If that's the case, could we fail nicely and display a message to the user?

[BoD]

Just making sure I understand here. Is this happening when the AKIJP version is not matching the AKGP version?

Exactly. (but I need to dig a bit more because it happened to me while I was on main, so latest AKGP)

Could we fail nicely and display a message to the user?

Yes we could probably gently nudge that they should update AKIJP (although IJ itself already nudges about plugin updates, so would probably be a nice-to-have but not very high priority)