Support generation of Job/CronJob resources

[Sgitario]

Fix #27024

[gsmet]

I haven't reviewed the code, only the documentation.

[gsmet]

@Sgitario I think you missed some of my suggestions. GitHub displays some of them in the Conversation tab but it hides those in the middle and you have to click on 14 hidden conversations Load more.

[Sgitario]

@Sgitario I think you missed some of my suggestions. GitHub displays some of them in the Conversation tab but it hides those in the middle and you have to click on 14 hidden conversations Load more.

Ops, sorry! All the suggestions are now applied.

[gsmet]

OK, I'll take it from there as I want to apply one more tab related change.

[gsmet]

I squashed the commits and also used the tabs for pom.xml/build.gradle alternatives in the Picocli doc.

[gsmet]

I'm good on the doc side, I will let @iocanel check the code itself.

[geoand]

@iocanel mind taking a look at this?

[iocanel]

we need to check that working with existing resources dont throw CME. A test maybe?

[Sgitario]

@iocanel as far I know, the decorators are applied sequentially, so don't think we should worry about concurrent modifications. Moreover, we're doing the same in other decorators. However, to be extra safe, I've added this test https://github.com/quarkusio/quarkus/blob/389d91b8170a30248954788d41201f80fc8c8c31/integration-tests/kubernetes/quarkus-standard-way/src/test/java/io/quarkus/it/kubernetes/KubernetesWithExistingCronJobResourceTest.java.

Btw, after rebasing the branch, I spotted an issue when applying the matching labels. I've already fixed it, but I need to fix it in Dekorate as well.

[quarkus-bot]

Failing Jobs - Building 52dfe16

Status	Name	Step	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✖	JVM Tests - JDK 11 Windows	Build	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 17
✔️	JVM Tests - JDK 18
✖	Quickstarts Compilation - JDK 17	Compile Quickstarts	Failures	Logs	Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 11 Windows #

- Failing: integration-tests/opentelemetry-reactive 

📦 integration-tests/opentelemetry-reactive

✖ io.quarkus.it.opentelemetry.reactive.OpenTelemetryReactiveClientTest.post line 94 - More details - Source on GitHub

org.opentest4j.AssertionFailedError: expected: <44fcf8d1b6a91bd3> but was: <500e364eaa3388ac>
	at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
	at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)

---

⚙️ Quickstarts Compilation - JDK 17 #

- Failing: optaplanner-quickstart 

📦 optaplanner-quickstart

✖ Failed to execute goal io.quarkus:quarkus-maven-plugin:999-SNAPSHOT:build (default) on project optaplanner-quickstart: Failed to build quarkus application

[iocanel]

@iocanel as far I know, the decorators are applied sequentially, so don't think we should worry about concurrent modifications. Moreover, we're doing the same in other decorators. However, to be extra safe, I've added this test

It doesn'matter how you apply the decorators. Modifying a list while iterating it will result in this exception. I think the same applies to stream. Eitherway, having a test is good enough for me.

[iocanel]

lgtm

[Sgitario]

Tests failures are unrelated. I'm merging this.