Use setPomFile method for setting pom file on MavenProject

setFile method also change basedir ... which can be a wrong here

Author: slawekjaranowski

maven-plugin-testing-harness/src/main/java/org/apache/maven/api/plugin/testing/MojoExtension.java

@@ -463,8 +463,15 @@ protected Mojo lookupMojo(
         }
 
         if (mockingDetails(mavenProject).isMock()) {
-            if (mockingDetails(mavenProject).isSpy() && pomPath != null) {
-                mavenProject.setFile(pomPath.toFile());
+            if (mockingDetails(mavenProject).isSpy()) {
+                // there is no setter for basedir, so set it via reflection
+                setVariableValueToObject(
+                        mavenProject, "basedir", Paths.get(getBasedir()).toFile());
+
+                // we only set the pom file
+                // setFile also change a basedir, so should not be used here
+                mavenProject.setPomFile(
+                        Optional.ofNullable(pomPath).map(Path::toFile).orElse(null));
             } else {
                 lenient()
                         .doReturn(new File(getTestBasedir(extensionContext)))