Find webpack 4 configuration that webpack 5 needs migrated by hand

Marks what the webpack 5 migration guide lists in a webpack configuration and the webpack 5 recipes do not change: NamedModulesPlugin, NamedChunksPlugin and HashedModuleIdsPlugin (now optimization options), IgnorePlugin called with a regular expression (now {resourceRegExp}), a node object with entries for core modules (now resolve.fallback, with a polyfill package where the module is needed; node.global, node.__filename and node.__dirname are still valid and not marked), and file-loader, url-loader and raw-loader rules that could not be converted to asset modules, such as those with options.