dynamically loaded "peer" dependency modules of direct dependencies are not added to the minimal package.jsn

for win32 platform, relative path imports imports made from node_modules that are set as 'external' are getting bundled

minimal package.json includes dependency peers as dependencies regardless if the peer module is already included in the base peerDependencies

module path is not updated for any lazy property imports made via import("...") using a dot relative path

the 'hash' plugin does not need to run if the 'emitNoHash' options is set

unused / un-configured plugins are getting instantiated when constructing the webpack configuration (although not initialized)

several issues when building for 'web' target

regression - previous release does not include the runtime.js file

regression - previous release does not include the runtime.js file

add new configurable base rc config option 'crypto' for data persistence encryption

add new configuration to support specification of what type of 'runtime' chunk is generated

add new cache group for bundled '@eslint' modules and isolate from common 'vendor' cache group

modify behavior for 'lib' type builds to bundle modules that are listed in package.json 'dependencies', and externalize modules listed in 'peerDependencies' and 'optionalDependencies', whereas previously all module dependencies were externalized without custom regexes configured in the rc 'externals' options configuration

adjust spmh bundle regexes to include 'vscode-utils' package into 'spmha' cached group

break down spmh library bundle into multiple, smaller chunks, now 'spmha' (app), 'spmhc' (common shared), and 'spmhl' (app / library)