fix: null-check LoggerDynamicMBean addAppender instantiation

[SebTardif]

LoggerDynamicMBean.addAppender (log4j-1.2-api JMX) calls OptionConverter.instantiateByClassName(..., null) and immediately uses the result. When the class name is invalid or not an Appender, instantiation returns null and the next line NPEs on appender.setName(...). That reaches the host through the JMX addAppender operation with a bad class name.

Failure scenario

// LoggerDynamicMBean.addAppender
final Appender appender =
    (Appender) OptionConverter.instantiateByClassName(appenderClass, Appender.class, null);
appender.setName(appenderName); // NPE when instantiate returns null

OptionConverter.instantiateByClassName already logs and returns the default (null) on ReflectiveOperationException or assignability failure. The JMX facade must treat that as "do not attach," not as a hard crash.

Fix

• Null-check after instantiate; cat.error(...) and return without attaching.
• Sibling audit: AppenderDynamicMBean.setLayout has the same instantiate pattern, but registerLayoutMBean already returns early when layout == null. No change needed there.

Red / green

# Without fix
./mvnw -pl log4j-1.2-api test \
  -Dtest=LoggerDynamicMBeanTest#addAppenderDoesNotNpeWhenClassCannotBeInstantiated \
  -Dsurefire.failIfNoSpecifiedTests=false
# FAIL: NPE at LoggerDynamicMBean.addAppender:70 setName on null

# With fix
./mvnw -pl log4j-1.2-api test -Dtest=LoggerDynamicMBeanTest \
  -Dsurefire.failIfNoSpecifiedTests=false
# PASS: Tests run: 2, Failures: 0

Also covers the happy path: valid ConsoleAppender class still attaches under the given name.

Checklist

• Base branch: 2.x
• Changelog: src/changelog/.2.x.x/fix_logger_dynamic_mbean_null_appender.xml
• Tests: LoggerDynamicMBeanTest (JUnit 5, same package as package-private addAppender)
• Spotless: ./mvnw spotless:check -pl log4j-1.2-api -am clean

Related: same null-from-instantiate class as #4172 (XmlConfiguration parseAppender).

[ramanathan1504]

@SebTardif Thank you for catching and fixing this NPE. This is your 4th PR, and we truly appreciate your ongoing support. If possible, could you consider picking up some items from the issue list? That would be incredibly helpful for our team. Of course, please continue submitting fixes for NPEs and other issues as you find them—they are always welcome. I will aim to review and close this PR this weekend.

[ramanathan1504]

LGTM!