[rgoers]

Add back a constructor that was removed that Spring Boot uses.

Fix LoggerUpdaterTest that was broken after a different PR was applied. Claude performed the fixes:
Changed two tests in LoggerUpdateTest.java:

• testUpdateLoggersPropertyListeners: it now keeps a reference to its configuration-started listener and removes it in a finally block.
• propertyChangeListenerReceivesOldAndNewConfigurationOnReconfiguration: in a finally block, it now removes its property-change listener and calls context.reconfigure().

[ramanathan1504]

The LoggerUpdateTest change is needed: on main the leaked configuration-started listener fails propertyChangeListenerReceivesOldAndNewConfigurationOnReconfiguration, and with the finally blocks the class passes.
The restored LoggerConfig(String, Level, boolean) passes a null configuration to the protected constructor, which calls config.getLogEventFactory(), so Spring Boot's LevelSetLoggerConfig now gets a NullPointerException instead of NoSuchMethodError. Where should it get its LogEventFactory and ReliabilityStrategy without a configuration, and can a test build one, add it with addLogger and log through it?

[ramanathan1504]

@rgoers Changelog also needed.
Thanks

[ramanathan1504]

The NPE is gone: a LoggerConfig from this constructor gets the context's configuration and logs after addLogger and updateLoggers.
Can LoggerUpdateTest get a test that does exactly that, with removeLogger in a finally? None of the current tests call this constructor, so a revert to null would stay green.