Make testLambdaCapturing test conditional on GraalVM version

[zakkak]

Starting with GraalVM 24.0 lambda class names match the ones from HotSpot.

Closes #37037

Being tested against GraalVM CE 24.0-dev in https://github.com/graalvm/mandrel/actions/runs/6860951487

[jerboaa]

Seems OK to me.

[zakkak]

Being tested against GraalVM CE 24.0-dev in https://github.com/graalvm/mandrel/actions/runs/6860951487

CI runs with 24.0-dev look good (the simple with space failure is tracked in #36998)

[quarkus-bot]

Failing Jobs - Building 4f6c97e

Status	Name	Step	Failures	Logs	Raw logs	Build scan
✔️	JVM Tests - JDK 11
✔️	JVM Tests - JDK 17
✖	JVM Tests - JDK 21	Build	Failures	Logs	Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 21 #

- Failing: extensions/micrometer/deployment 
! Skipped: extensions/micrometer-registry-prometheus/deployment extensions/quartz/deployment extensions/scheduler/deployment and 25 more

📦 extensions/micrometer/deployment

✖ io.quarkus.micrometer.deployment.binder.VertxHttpClientMetricsTest.testWebClientMetrics line 56 - More details - Source on GitHub

java.util.concurrent.CompletionException: java.net.BindException: Address already in use
	at io.smallrye.mutiny.operators.uni.UniBlockingAwait.await(UniBlockingAwait.java:79)
	at io.smallrye.mutiny.groups.UniAwait.atMost(UniAwait.java:65)