Disable build scan publication for test builds

[jprinet]

Issue

The Quarkus build is comprised of many test builds which by default publish some build scans to Gradle Enterprise.
The current approach only publish those test builds when failing. This is however not sufficient as some tests are expecting builds to fail.

Fix

As described here, use the -Dscan=false system property where required

[maxandersen]

why set it here?

[jprinet]

Some smoke tests are triggering some Maven builds which would publish some build scans.

[maxandersen]

not great we have to change the code this much (its not a lot but also more than nothing ;) but if no other way to avoid the scan to be submitted I guess we have to go for this approach.

I would have preferred a way to detect it in the groovy rules.

but +1 on this if no better alternative

[jprinet]

not great we have to change the code this much (its not a lot but also more than nothing ;) but if no other way to avoid the scan to be submitted I guess we have to go for this approach.

I would have preferred a way to detect it in the groovy rules.

but +1 on this if no better alternative

This is the best we have so far if we want to make sure no test builds are published

[jprinet]

Let's pause this for a second, there might be a simpler option using the Groovy script

I convert this PR to draft and propose a new version ASAP

[quarkus-bot]

Failing Jobs - Building 50a1f35

Status	Name	Step	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✔️	JVM Tests - JDK 17
⌛	JVM Tests - JDK 17 Windows	Build	⚠️ Check →	Logs	Raw logs
✔️	JVM Tests - JDK 19
✔️	Maven Tests - JDK 11
⌛	Maven Tests - JDK 11 Windows	Build	⚠️ Check →	Logs	Raw logs

[jprinet]

Closing in favor of #34335