Deprecate fullStacktraces

[jerboaa]

GraalVM 23.1+ will have this option deprecated doing nothing. Deprecate it in Quarkus as well.

See for example this CI run:
https://github.com/graalvm/mandrel/actions/runs/5227497104/jobs/9439379340#step:12:140

Fixes: Karm/mandrel-integration-tests#167

[quarkus-bot]

Failing Jobs - Building d4bcd81

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

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 17 Windows #

- Failing: extensions/amazon-lambda/deployment 
! Skipped: extensions/amazon-lambda-http/deployment extensions/amazon-lambda-rest/deployment integration-tests/amazon-lambda and 6 more

📦 extensions/amazon-lambda/deployment

✖ io.quarkus.amazon.lambda.deployment.testing.LambdaDevServicesContinuousTestingTestCase.testLambda line 48 - More details - Source on GitHub

org.opentest4j.AssertionFailedError: expected: <1> but was: <0>
	at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
	at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)

---

⚙️ JVM Tests - JDK 19 #

- Failing: extensions/amazon-lambda/deployment 
! Skipped: extensions/amazon-lambda-http/deployment extensions/amazon-lambda-rest/deployment integration-tests/amazon-lambda and 6 more

📦 extensions/amazon-lambda/deployment

✖ io.quarkus.amazon.lambda.deployment.testing.LambdaDevServicesContinuousTestingTestCase.testLambda line 48 - More details - Source on GitHub

org.opentest4j.AssertionFailedError: expected: <1> but was: <0>
	at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
	at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)

[jerboaa]

CI failures seem unrelated.

[jerboaa]

@geoand FWIW, @zakkak is away for while. If somebody else could have a look too, it would be good. @galderz or @Karm perhaps?

[galderz]

Looks good, thanks @jerboaa

[zakkak]

Given that we are still on 23.0, shouldn't we delay the deprecation?

[jerboaa]

No, I think this is still fine. Users need a way to become aware. Deprecating it now is the right call, imo. On the next release using it would do nothing.