fix: missing logging after dependencies bump

[psmagin]

Purpose

Fix logging missing

Approach

After the dependabot bump, the classpath ordering changed — log4j-core (position 25) now appears before okapi-common (position 46) in the Maven classpath. The maven-shade-plugin processes JARs in classpath
order and last-write-wins for conflicting files. This caused okapi-common's Log4j2Plugins.dat (which only contains FolioLoggingContext) to overwrite log4j-core's full plugin cache. With no Console or PatternLayout
plugins registered, log4j2 couldn't create the configured appender — complete silence.

Before the commit the order was reversed (okapi-common: 42, log4j-core: 104), so log4j-core won and logging worked.

Changes Checklist

• API Changes: Document any API paths, methods, request or response bodies changed, added, or removed.
• Database Schema Changes: Indicate any database schema changes and their impact. Confirm that migration scripts were created.
• Interface Version Changes: Indicate any changes to interface versions.
• Interface Dependencies: Document added or removed dependencies.
• Permissions: Document any changes to permissions.
• Logging: Confirm that logging is appropriately handled.
• Unit Testing: Confirm that changed classes were covered by unit tests.
• Integration Testing: Confirm that changed logic was covered by integration tests.
• Manual Testing: Confirm that changes were tested on local or dev environment.
• NEWS: Confirm that the NEWS file is updated with relevant information about the changes made in this pull request.

Related Issues

https://folio-org.atlassian.net/browse/MODINV-1411

Screenshots

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud