Reset the fallback listener on StatusLogger#reset()

[vy]

The issue was initially caused by #2249. This fix also addresses the CI failures on Windows.

[ppkarwasz]

This looks good to me: it solves the immediate problem, although I would probably prefer for StatusConsoleListeners to be replaced instead of reconfigured.

The problem of resetting the StatusConsoleListener is however more general: since the constructors of several Configuration objects mess with the fallback StatusConsoleListener, logger contexts should call StatusLogger.reset() at shutdown:

logging-log4j2/log4j-core/src/main/java/org/apache/logging/log4j/core/LoggerContext.java

Lines 383 to 390 in c6832d6

	final Configuration prev = configuration;
	configuration = NULL_CONFIGURATION;
	updateLoggers();
	if (prev instanceof LifeCycle2) {
	((LifeCycle2) prev).stop(timeout, timeUnit);
	} else {
	prev.stop();
	}

If we fix the lines above, most calls to StatusLogger#reset in our tests should become useless.

I am not sure what to do during reconfiguration:

logging-log4j2/log4j-core/src/main/java/org/apache/logging/log4j/core/LoggerContext.java

Lines 631 to 637 in 90cf8e7

	config.start();
	this.configuration = config;
	updateLoggers();
	if (prev != null) {
	prev.removeListener(this);
	prev.stop();
	}

Here the new configuration already change the fallback status listener settings, so we probably don't need to do anything.

[vy]

This looks good to me: it solves the immediate problem, although I would probably prefer for StatusConsoleListeners to be replaced instead of reconfigured.

I explained why this is not possible in this conversation.

logger contexts should call StatusLogger.reset() at shutdown

StatusLogger is [statically] shared between all LoggerContexts. Hence, are you sure resetting the StatusLogger singleton when a LoggerContext shuts down is the right thing to do?

[vy]

After a video call with @ppkarwasz, we decided to proceed with this PR as it is. A good step forward would be to remove StatusConfiguration in main.