Fix Runner Warning: `SLF4J: Class path contains multiple SLF4J bindings.`

[TobiasNx]

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/tobias/Downloads/metafix-runner-1.1.2/lib/slf4j-reload4j-1.7.36.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/tobias/Downloads/metafix-runner-1.1.2/lib/slf4j-simple-1.7.21.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Reload4jLoggerFactory]

The runner build by core does not have this warning. Not sure if this is related to: metafacture/metafacture-fix#371 (comment)

[TobiasNx]

Found at least one source of this warning. The warning is only appearing when the record has a fix method:

NO Warning:

"http://sru.hebis.de/sru/DB=2.1?query=pica.ort+%3D+%22Mainz%22+and+pica.ppn+%3D+%22524204101%22&version=1.1&operation=searchRetrieve&stylesheet=http%3A%2F%2Fsru.hebis.de%2Fsru%2F%3Fxsl%3DsearchRetrieveResponse&recordSchema=marc21&maximumRecords=10&startRecord=1&recordPacking=xml&sortKeys=LST_Y%2Cpica%2C0%2C%2C"
| open-http(accept="application/xml")
| decode-xml
| handle-marcxml
| encode-json(prettyPrinting="true")
| print
;

Shows Warning:

SRUQUERRY = "http://sru.hebis.de/sru/DB=2.1?query=pica.ort+%3D+%22Mainz%22+and+pica.ppn+%3D+%22524204101%22&version=1.1&operation=searchRetrieve&stylesheet=http%3A%2F%2Fsru.hebis.de%2Fsru%2F%3Fxsl%3DsearchRetrieveResponse&recordSchema=marc21&maximumRecords=10&startRecord=1&recordPacking=xml&sortKeys=LST_Y%2Cpica%2C0%2C%2C";

SRUQUERRY
| open-http(accept="application/xml")
| decode-xml
| handle-marcxml
| fix("nothing()")  // DUE TO THE INTRODUCTION OF FIX.
| encode-json(prettyPrinting="true")
| print
;

[TobiasNx]

@blackwinter this might be relevant when migrating fix to core:

#577

[TobiasNx]

I tried to test it with the new integration of fix into core but it does not work yet: #586 (comment)

[blackwinter]

Functional review: @TobiasNx
Code review: @dr0i