Create a new lightweight goal/task that evaluates all the configuration and creates the liberty-plugin-config.xml potentially without installing Liberty itself and without creating the server itself

Problem statement: When the end user edits Liberty configuration files in a new project that has not been built yet, certain information about the project is not known in LCLS and Liberty Tools. The key information not known has to due with what Liberty is being used (Open Liberty or WebSphere Liberty, what version?), which configuration files and properties are being used (the LMP/LGP does a lot of processing and combining of information included in the build file for configuration such as server.env, bootstrap.properties, jvm.options, and the server config files themselves).

To know the true effective configuration in use by the project, the create server goal/task must be run at a minimum and that automatically does the Liberty install before copying over all the config to the newly created server. Once that is done, the liberty-plugin-config.xml file exists in the target/build directory and contains vital information about the configuration that can be used by LCLS/Liberty Tools when doing diagnostics.

Solution: Create a new lightweight goal/task that evaluates all the configuration and creates the liberty-plugin-config.xml potentially without installing Liberty itself and without creating the server itself , but mocking the server structure so that variable processing can be done

Similar goal is suggested as part of https://github.com/OpenLiberty/ci.maven/issues/1094