fix(@angular-devkit/build-angular): ensure all SSR chunks are resolve…

…d correctly with dev server

The `server-utils` SSR generated chunk was not previously included in the ESM in memory loader for
prerendering which resulted in the ESM resolver incorrectly attempting to resolve non-relative
dependencies. This would lead to resolution errors when using the development server with caching
enabled. In this scenario, the Angular dependencies would be marked external and the server utilities
output chunk would contain non-relative imports and fail to prerender.

(cherry picked from commit 974acb7)

packages/angular_devkit/build_angular/src/utils/server-rendering/esm-in-memory-loader/loader-hooks.ts

@@ -23,7 +23,7 @@ export interface ESMInMemoryFileLoaderWorkerData {
 }
 
 const TRANSFORMED_FILES: Record<string, string> = {};
-const CHUNKS_REGEXP = /file:\/\/\/(main\.server|chunk-\w+)\.mjs/;
+const CHUNKS_REGEXP = /file:\/\/\/((?:main|render-utils)\.server|chunk-\w+)\.mjs/;
 let workspaceRootFile: string;
 let outputFiles: Record<string, string>;