Add something like `JavaParser.dependsOn` for Maven recipes tests or a way to bypass dependency checks

I was trying to write a recipe test for a recipe involving an artifactId change using ChangeDependencyGroupIdAndArtifactId recipe.

My problem is that new artifactId is not released yet, so it's not downloadable from any repo (company repo in this case) yet. Additionally, to be able to download from our company maven repository, I guess I need to specify -Dorg.openrewrite.test.readMavenSettingsFromDisk and so on...

Would it be possible to add something like JavaParser.dependsOn to avoid needing to really download any dependency from any repo and work fully offline for tests? Or just a way to disable any dependency check and just work with pom.xml as an agnostic XML file?

What is more weird for me is that the recipe works 100% OK when launched on a real project, so there is no dependency download there and the final pom.xml will have the new artifactId in place, pointing to a not downloadable dependency. No problem for this, openRewrite did the job ok.

Start with the Maven recipe test setup involving ChangeDependencyGroupIdAndArtifactId and compare it with JavaParser.dependsOn. Investigate how dependency checks and Maven settings are applied in tests, then determine whether an offline bypass or agnostic pom.xml mode can support an unreleased artifactId. Done means the recipe test runs without downloading the unavailable dependency and still verifies the updated pom.xml.