Log4j's implementation of SLF4J `Logger` should not use no-op builders

The fix for [LOG4J2-3647](https://issues.apache.org/jira/browse/LOG4J2-3647) didn't include an equivalent fix for our SLF4J binding. An SLF4J call:

```lang-java
logger.atDebug()...
```
discards all messages less specific than `DEBUG`, even those messages that would be accepted by a global filter.

The equivalent Logback issue is [LOGBACK-1719](https://jira.qos.ch/browse/LOGBACK-1719).

This issue was reported in this [StackOverflow question](https://stackoverflow.com/q/75556273/11748454).