CurseUpload4J debug mode logs as `ERROR`

[MattSturgeon]

We use CurseUpload4J's debug mode when using --dry-run. Currently, it uses an SLF4J logger and logs to logger.error(). This leads to noisy red output locally and a lot of GHA ::error:: annotations in CI.

• Consider adding a Slf4jAdapter hook that remaps log levels (hack)
• Consider contributing a logLevel (slf4j Level) field upstream
• Consider contributing a logConsumer (Consumer<String>) override upstream

The Consumer approach would also mean we don't need our Slf4jAdapter at all (and we could probably exclude upstream's log4j transitive dependency?)

cc upstream: @hypherionmc

[hypherionmc]

The logger in CurseUpload4j uses plain SLF4J, whereas gradle uses a modified version of it.

Under normal conditions, gradle wouldn't log any other output from different levels, hence the use of error. Ideally I should add support for passing a Gradle based slf4j logger into the library, which routes the error to lifecycle instead

[MattSturgeon]

Sorry, I tagged you in this issue without giving you any context.

Here, we're not using gradle or slf4j. We have our own Logger, and I implemented Slf4jAdapter solely for injecting a logger into CurseUploadApi:

Publisher/curseforge/src/main/kotlin/net/xolt/freecam/publish/platforms/CurseForgeClient.kt

Line 28 in 9c516ad

api = CurseUploadApi(config.token, logger.slf4j).apply {

All I really need though is to inject a "log consumer" function. The default function could use an SLF4J logger.error(), and my injected one could use my logger.