CLI: add an option to generate a simple build report

[mkouba]

• resolves CLI - add an option to generate the build report #29174

[gsmet]

Works as advertised but I suggested a few improvements.

[mkouba]

@gsmet Is the Native Tests - Security2 failure a known flaky test?

[quarkus-bot]

Failing Jobs - Building 2aef8e9

Status	Name	Step	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✔️	JVM Tests - JDK 17
✖	JVM Tests - JDK 17 Windows	Build	Failures	Logs	Raw logs
✖	JVM Tests - JDK 20	Build	⚠️ Check →	Logs	Raw logs
✖	Native Tests - Security2	Build	Failures	Logs	Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 17 Windows #

- Failing: extensions/grpc/deployment 
! Skipped: extensions/micrometer-registry-prometheus/deployment extensions/micrometer/deployment extensions/opentelemetry/deployment and 52 more

📦 extensions/grpc/deployment

✖ io.quarkus.grpc.server.MutinyGrpcServiceWithSSLTest.testEmptyWithMutinyClient - More details - Source on GitHub

io.smallrye.mutiny.TimeoutException
	at io.smallrye.mutiny.operators.uni.UniBlockingAwait.await(UniBlockingAwait.java:64)
	at io.smallrye.mutiny.groups.UniAwait.atMost(UniAwait.java:65)

---

⚙️ Native Tests - Security2 #

- Failing: integration-tests/oidc 

📦 integration-tests/oidc

✖ io.quarkus.it.keycloak.BearerTokenAuthorizationInGraalITCase.testSecureAccessSuccessWithCors - More details - Source on GitHub

java.lang.AssertionError: 
1 expectation failed.
Expected status code <200> but was <404>.

[mkouba]

I'm going to merge this pull request since the BearerTokenAuthorizationInGraalITCase from the Native Tests - Security2 seems to fail in other PRs as well and the failure in JVM Tests - JDK 17 Windows is a timeout.