[WFCORE-4359] Ensure the CLI embedded stdio and log contexts are used for CLI loggers.

[jamezp]

WFCORE-4358

This commit just upgrades the log manager with a single commit to expose the LogContext.getLogContextSelector() which is required for the second commit.

WFCORE-4358

This commit fixes the issue where the incorrect log context could be used when creating CLI loggers and the incorrect StdioContext being used when CLI writes log messages.

Instead of just wrapping the current LogContext this wraps the CLI ThreadLocalContextSelector instead to ensure the correct contexts are used. I tested both the embed-server and embed-host-controller with the jboss-cli.sh script and the jboss-cli-client.jar. Log messages from CLI will now use the jboss-cli-logging.properties configuration (assuming that's used) and log messages from the server us the correct contexts from the server itself.

@jfdenise Could you please have a look and approve this?

[wildfly-ci]

Core - Full Integration Build 8395 outcome was FAILURE using a merge of 50b983f
Summary: Exit code 1 (Step: Build & test full (Maven)) (new) Build time: 00:02:54

[jamezp]

Note the ModuleInfoTestCase.testModuleInfo consistently fail when a log manager upgrade is done. It's due to the dependency not being found in the repository cache. It can be manually done or the tests can be run the next day after the cache is replicated.