Fix log injection smoke test flakiness under CI load (#10999)

Fix log injection smoke test flakiness under CI load

Increase BaseApplication.TIMEOUT_IN_NANOS from 10s to 30s to align with the
test's PollingConditions timeout (also 30s).

This is the only smoke test with a bidirectional handshake: the app blocks
waiting for remote config changes, and the test blocks waiting for traces.
Under CI load, the trace writer's first flush (including feature discovery)
can exceed 10s. When the app's timeout fires first, it crashes the process,
killing the daemon trace-writer thread before it delivers traces — so
traceCount stays at 0. Aligning both timeouts to 30s ensures the test's
polling condition is always the binding constraint, preventing the app from
independently crashing.

Observed across all JDK versions (8, 11, 17, 21, 25) — 17 failures in the
last 30 days.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Co-authored-by: devflow.devflow-routing-intake <devflow.devflow-routing-intake@kubernetes.us1.ddbuild.io>

Author: bm1549

dd-smoke-tests/log-injection/src/main/java/datadog/smoketest/loginjection/BaseApplication.java

@@ -10,7 +10,7 @@
 import java.util.function.Supplier;
 
 public abstract class BaseApplication {
-  public static final long TIMEOUT_IN_NANOS = TimeUnit.SECONDS.toNanos(10);
+  public static final long TIMEOUT_IN_NANOS = TimeUnit.SECONDS.toNanos(30);
 
   public abstract void doLog(String message);