Support additional recipe artifacts in quarkus update

[vsevel]

This is adding support for a updateRecipeArtifactCoordinates property in maven/gradle/cli for quarkus update, which allows to specify several artifacts containing update recipes.

this as been tested so far with mvn io.quarkus:quarkus-maven-plugin:999-SNAPSHOT:update -N -DupdateRecipeArtifactCoordinates=org.acme:quarkusupdate:1.0.0-SNAPSHOT,io.quarkus:quarkus-update-recipes:LATEST -DrewriteDryRun=true

with a 3.12.yaml recipe file in module org.acme:quarkusupdate containing:

---
type: [specs.openrewrite.org/v1beta/recipe](http://specs.openrewrite.org/v1beta/recipe)
name: add property foo
recipeList:
  - org.openrewrite.maven.AddProperty:
      key: foo
      value: bar
      preserveExistingValue: true

when running against a 3.8.5 project, this produces the following build log:

[INFO] Running recipe(s)...
[WARNING] These recipes would make changes to pom.xml:
[WARNING]     io.quarkus.openrewrite.Quarkus
[WARNING]         org.openrewrite.maven.UpgradeDependencyVersion: {groupId=io.quarkus.platform, artifactId=quarkus-bom, newVersion=3.12.0}
[WARNING]         io.quarkus.updates.core.quarkus39.Relocations
[WARNING]             org.openrewrite.java.dependencies.ChangeDependency: {oldGroupId=io.quarkus, oldArtifactId=quarkus-resteasy-reactive, newArtifactId=quarkus-rest}
[WARNING]         add property foo
[WARNING]             org.openrewrite.maven.AddProperty: {key=foo, value=bar, preserveExistingValue=true}
[WARNING]         io.quarkus.updates.core.quarkus310.UpdateConfigPackagePom
[WARNING]             io.quarkus.updates.core.quarkus310.AdjustPackageProperty
[WARNING] Patch file available:
[WARNING]     /Users/vsevel/dev/tmp/quarkusupdate/target/rewrite/rewrite.patch
[WARNING] Estimate time saved: 5m
[WARNING] Run 'mvn rewrite:run' to apply the recipes.

and the diff looks like:

% cat /Users/vsevel/dev/tmp/quarkusupdate/target/rewrite/rewrite.patch
diff --git a/pom.xml b/pom.xml
index 8560607..ffffd24 100644
--- a/pom.xml
+++ b/pom.xml
@@ -7,12 +7,13 @@ org.openrewrite.config.CompositeRecipe
   <version>1.0.2-SNAPSHOT</version>
   <properties>
     <compiler-plugin.version>3.13.0</compiler-plugin.version>
+    <foo>bar</foo>
     <maven.compiler.release>17</maven.compiler.release>
     <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
     <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
     <quarkus.platform.artifact-id>quarkus-bom</quarkus.platform.artifact-id>
     <quarkus.platform.group-id>io.quarkus.platform</quarkus.platform.group-id>
-    <quarkus.platform.version>3.8.5</quarkus.platform.version>
+    <quarkus.platform.version>3.12.0</quarkus.platform.version>
     <skipITs>true</skipITs>
     <surefire-plugin.version>3.2.5</surefire-plugin.version>
   </properties>
@@ -34,7 +35,7 @@
     </dependency>
     <dependency>
       <groupId>io.quarkus</groupId>
-      <artifactId>quarkus-resteasy-reactive</artifactId>
+      <artifactId>quarkus-rest</artifactId>
     </dependency>
     <dependency>
       <groupId>io.quarkus</groupId>
@@ -114,7 +115,8 @@
       </activation>
       <properties>
         <skipITs>false</skipITs>
-        <quarkus.package.type>native</quarkus.package.type>
+        <quarkus.native.enabled>true</quarkus.native.enabled>
+        <quarkus.package.jar.enabled>false</quarkus.package.jar.enabled>
       </properties>
     </profile>
   </profiles>

gradle support has not been done yet.
this has not been rebased onto the other PR (wondering if we really need to).
some logging has been added for debugging purposes, but will be removed before merge.
this is created as a draft to get some early feedback from @ia3andy

[ia3andy]

If you keep the other PR and rename the param to additionalRecipeCoords, then you don't need to specify the quarkus core one

[vsevel]

we can change the attribute to be additionalRecipeCoords, and always include the io.quarkus:quarkus-update-recipes. this is a good idea. I will go ahead and change that.
the other PR is not required unless we want to offer the ability to not use the default quarkus-update-recipes. this is not a requirement I have (but others might?).

[vsevel]

changed naming to additionalUpdateRecipeCoords

[vsevel]

should be ready for review.
tested with mvn io.quarkus:quarkus-maven-plugin:999-SNAPSHOT:update -N -DadditionalUpdateRecipeCoords=org.acme:quarkusupdate:1.0.3-SNAPSHOT -DrewriteDryRun=true
if no comments, I need to get rid of the extra logs, plus squash/rebase

[ia3andy]

it looks good !

[vsevel]

I cleaned the logs, squashed and rebased. I am wondering if we should keep the clean in the process-sources command.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 0ae63d5.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

[vsevel]

CI finally green @gsmet

[ia3andy]

@vsevel wait we might need to rename again following @maxandersen review:

And I suggest it becomes:
updateRecipe and additionalUpdateRecipes to signal one is singular the other plural/list.

[ia3andy]

@vsevel ok since there is no release planned, let's merge this and I'll rename both in my following PR

Thanks for this!!