fix: Clean up Apache Lucene logging via SLF4j redirect

[chadlwilson]

Also suppresses the default logs for users.

Description of Change

Currently there are occasional logs (especially from the Apache Lucene indexing) that are coming through in an consistent format. They are mostly due to warnings about the JVM-in-use (due to use of Azul/Zulu JVM within the docker image rather than Hotspot/Temurin/OpenJDK etc).

• Added jul-to-slf4j bridge
• Initialised during Lucene initialization as this seems to be the main JUL dependency, and I couldn't think of a better init location that works across CLI, Maven, Gradle etc.
  • Technically there do seem to be other libraries potentially using java.util.logging, so it might be a better idea to get the logging set up within the Engine or the AbstractAnalyzer if these are the main entry points to core
• Removed slf4j-simple dependency management definition (unused)
• Stopped logging lucene errors unless at ERROR level on CLI since these errors are somewhat far from being user-addressable, and inevitable on the Docker image. This change is up for debate.

Before (via CLI on temurin-21 in docker image)

[INFO] Finished Version Filter Analyzer (0 seconds)
Sep 25, 2025 8:40:55 AM org.apache.lucene.util.HotspotVMOptions <clinit>
WARNING: Lucene cannot optimize algorithms or calculate object sizes for JVMs that are not based on Hotspot or a compatible implementation.
WARNING: A restricted method in java.lang.foreign.Linker has been called
WARNING: java.lang.foreign.Linker::downcallHandle has been called by the unnamed module
WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for this module

Sep 25, 2025 8:40:56 AM org.apache.lucene.store.MemorySegmentIndexInputProvider <init>
INFO: Using MemorySegmentIndexInput and native madvise support with Java 21 or later; to disable start with -Dorg.apache.lucene.store.MMapDirectory.enableMemorySegments=false
Sep 25, 2025 8:40:56 AM org.apache.lucene.internal.vectorization.VectorizationProvider lookup
WARNING: Java runtime is not using Hotspot VM; Java vector incubator API can't be enabled.

You'll get varying different warnings depending on OpenJDK vs Zulu and different versions.

After - without Lucene log suppression (via CLI)

[INFO] Finished Version Filter Analyzer (0 seconds)
[WARN] Lucene cannot optimize algorithms or calculate object sizes for JVMs that are not based on Hotspot or a compatible implementation.
WARNING: A restricted method in java.lang.foreign.Linker has been called
WARNING: java.lang.foreign.Linker::downcallHandle has been called by the unnamed module
WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for this module

[INFO] Using MemorySegmentIndexInput and native madvise support with Java 21 or later; to disable start with -Dorg.apache.lucene.store.MMapDirectory.enableMemorySegments=false
[WARN] Java runtime is not using Hotspot VM; Java vector incubator API can't be enabled.

After - with warning suppression (via CLI)

[INFO] Finished Version Filter Analyzer (0 seconds)
WARNING: A restricted method in java.lang.foreign.Linker has been called
WARNING: java.lang.foreign.Linker::downcallHandle has been called by the unnamed module
WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for this module

Related issues

Partially addresses #7759 but does not address the JVM warnings.

Have test cases been added to cover the new functionality?

no

[jeremylong]

LGTM