Align properties of websmith CLI and webpack-loader options

[jwloka]

Suggestion

websmith in the current version uses different names, value types and even structure in configuration properties. We should align the properties in CompilerOptions and CompilationConfig with the properties in PluginArguments to use similar if not the same naming and structure.

✅ Viability Checklist

My suggestion meets these guidelines:

• This wouldn't be a breaking change in existing websmith addons
• This wouldn't negatively impact the performance of the websmith build process without opt-in

Existing addons wouldn't be affected by the change, but existing configuration need be adjusted

⭐ Suggestion

• Move and rename CompilationConfig#configFilePath to CompilerOptions#configFile.
• Change PluginArguments#addons to string[]
• Rename PluginArguments#config to PluginArguments#configFile
• Add PluginArguments#config: CompilationConfig
• Add PluginArguments#tsConfig: tsCompilerOptions
• Change PluginArguments#targets to string[]
• Rename PluginArguments to WebsmithLoaderOptions
• Rename PluginOptions to WebsmithLoaderConfig

All added and changed properties should remain optional.

📃 Motivating Example

After this refactoring the configurations would almost look the same:

compilerConfig = {
    targets: ["*"],
    configFile: path.join(OUTPUT_DIR, "websmith.config.json"),
    config: {
        addonsDir: ADDONS_DIR,
        addons: ["example-transformer"],
        targets: {
            "target-expected": {
                addons: ["example-transformer"],
            },
        },
    },
};
loaderConfig = {
    targets: ["*"],
    webpackTarget: "*",
    configFile: path.join(OUTPUT_DIR, "websmith.config.json"),
    config: {
        addonsDir: ADDONS_DIR,
        addons: ["example-transformer"],
        targets: {
            "target-expected": {
                addons: ["example-transformer"],
            },
        },
    }.
}