fix: Mute noisy logging from Apache Lucene

[chadlwilson]

Within Gradle we cannot really control the SLF4J logging on behalf of the user, as Gradle uses its own custom implementation. However we can control that for the java.util.logging libraries since JUL allows mutating levels at runtime; so we can mute things before they are propagated to SLF4J via Gradle's interceptors.

This is an analogous change to dependency-check/DependencyCheck#8248 for ant/maven.

Sadly, can't find a way to do anything about Apache HTTPClient which makes the Gradle --debug logging impossible to parse/use with ODC (since it basically logs all responses at debug rather than trace level).

This avoids logging in the Gradle lifecycle of stuff like the first line of the below

You are running with Java 23 or later. To make full use of the Vector API, please update Apache Lucene.
Found 0 vulnerabilities in project gocd

[Copilot]

Pull request overview

This PR adds logging configuration to mute noisy output from Apache Lucene in Gradle builds. Since Gradle uses its own logging system and custom SLF4J implementation, this change directly configures java.util.logging (JUL) to suppress Lucene's verbose messages at the SEVERE level before they reach Gradle's logging infrastructure.

Changes:

• Added a static initializer block to DependencyCheckPlugin that configures java.util.logging to mute Apache Lucene loggers
• Imported necessary java.util.logging classes (Level, LogManager) and StandardCharsets for configuration

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.