Properly handle gradle include build null project in dependency collection

Ensure that `initProjectModuleAndBuildPaths` throws an
`IllegalStateException` with a clear message if the provided
Gradle `Project` is null.

This will help in diagnosing issues related to missing projects
when resolving dependencies in Gradle builds, especially
in the context of included builds.

Author: drmaniac

devtools/gradle/gradle-model/src/main/java/io/quarkus/gradle/tooling/GradleApplicationModelBuilder.java

@@ -518,7 +518,10 @@ private void collectDependencies(org.gradle.api.artifacts.ResolvedDependency res
 
     private void initProjectModuleAndBuildPaths(final Project project,
             ResolvedArtifact resolvedArtifact, ApplicationModelBuilder appModel, final ResolvedDependencyBuilder appDep) {
-
+        if (project == null) {
+            System.err.println("Error: could not find project for " + resolvedArtifact.getId().getDisplayName());
+            throw new IllegalStateException("Could not find project for " + resolvedArtifact.getId().getDisplayName());
+        }
         appDep.setWorkspaceModule().setReloadable();
 
         if (appDep.getWorkspaceModule() == null) {