Consider making plugin builds less chatty

Our build has custom plugins and this is the output we have on a regular Gradle build:

```
Note: GraalVmProcessor: writing GraalVM metadata for 12 Java classes to `META-INF/native-image/log4j-generated/org.springframework.boot/spring-boot-log4j/reflect-config.json`.
Note: PluginProcessor: writing plugin descriptor for 13 Log4j Plugins to `META-INF/org/apache/logging/log4j/core/config/plugins/Log4j2Plugins.dat`.
```

One thing that always tricks me is that I often forgets it is about log4j, especially reading "Note: GraalVmProcessor: writing GraalVM metadata for 12 Java classes".

Can you please consider this to be less chatty? Do we really need that log by default? If we really do, can't we do something to make it a bit more obvious that it is log4j doing something during the build? Thank you

Start by examining the GraalVmProcessor and PluginProcessor messages shown in the issue during a regular Gradle build. The issue leaves open whether to suppress the messages by default or make Log4j's involvement clearer; done means addressing that concern, with the behavior made clear to the reporter.

Written by the indexing model from the issue text.