refactor(@angular-devkit/build-angular): remove Webpack loader resolve custom setting

The Webpack configuration setup previously walked up the directory structure to find all `node_modules` directories and then pass this list to Webpack's `resolverLoader.modules` option. This was previously done to ensure that hoisted packages were properly resolved. However, all loader paths are now fully resolved prior to being added to the Webpack configuration. Since loader paths will now be absolute, Webpack no longer needs to resolve them which makes the resolve settings no longer necessary.

Author: clydin

packages/angular_devkit/build_angular/src/utils/find-up.ts

@@ -41,7 +41,6 @@ import {
   persistentBuildCacheEnabled,
   profilingEnabled,
 } from '../../utils/environment-options';
-import { findAllNodeModules } from '../../utils/find-up';
 import { Spinner } from '../../utils/spinner';
 import { addError } from '../../utils/webpack-diagnostics';
 import { DedupeModuleResolvePlugin, ScriptsWebpackPlugin } from '../plugins';
@@ -359,13 +358,6 @@ export function getCommonConfig(wco: WebpackConfigOptions): Configuration {
     },
     resolveLoader: {
       symlinks: !buildOptions.preserveSymlinks,
-      modules: [
-        // Allow loaders to be in a node_modules nested inside the devkit/build-angular package.
-        // This is important in case loaders do not get hoisted.
-        // If this file moves to another location, alter potentialNodeModules as well.
-        'node_modules',
-        ...findAllNodeModules(__dirname, projectRoot),
-      ],
     },
     context: root,
     entry: entryPoints,