builds not of type 'app' or 'lib' are failing on invalid optimization export config

changes to entry configuration definitions causing several issues

builds of type 'lib' are emitting output files with the contenthash still in the filename

entry filename mutation is adding hash value from first processed asset and not considering file extension

npm and vsce iso release should dynamically adjust entry filename and path, e.g. inserting a contenthash into the filename and/or adjusting the relative path of the values in the 'export', 'main' and/or 'module' properties in package.json

command line option to specify browser path doesnt work

regression - startup fails if the 'test' property is not defined in rc config file

enable terser for al transpiled builds to execute some tasks other than minification, compression and/or mangling, even if 'minification' is disabled

move adding shebang to 'additions' stage of compilation 'processAssets' hook, previously it was at 'optimize_inline' due to unknown issue in terser removing the shebang, the solution to this was finally found and corrected in the minification configuration

add new rc config property 'autoConfig' to allow disabling of all auto-configuration at startup

regression - add check and auto add beginning dot to path name for entry point configuration