build: migrate @angular-devkit/build-angular tests to rules_js

[devversion]

Migrates the @angular-devkit/build-angular tests to rules_js. This was a rather larger undertaking as the tests were very reliant on e.g. the directory structure or specific node module layout; so some changes were needed.

• the Sass files include a much larger file header now. That is because the npm Sass files have much larger paths, given being inside a symlinked pnpm store directory. E.g.

/*!**********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************!*\
  !*** css ../../../../../node_modules/.aspect_rules_js/[email protected]_webpack_5.97.1/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[4].rules[0].oneOf[0].use[1]!../../../../../node_modules/.aspect_rules_js/[email protected]_1462687623/node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[4].rules[0].oneOf[0].use[2]!./src/test-style-a.css?ngGlobalStyle ***!
  \**********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************/
.test-a {color: red}

• Similarly to above, hashed chunk files can change given different paths of e.g. Webpack, or external sources.

• Tests for verifying the lazy module chunks may enable preserveSymlinks just to make the chunk names shorter and easier to verify, avoiding truncatd super long paths to the e.g. pnpm stores again.

• the ngsw-worker.js file cannot be copied using copyFile as that results in permissions being copied as well. In Bazel, now that the npm files are properly captured, are readonly, so subsequent builds (e.g. the watch tests) will fail to copy/override the file again! Reading and writing the file consistently seems appropriate.

• Tests relying on puppeteer and webdriver-manager worked in the past, by accident, because postinstall scripts (from e.g. puppeteer) were able to modify content of other packages (e.g. the puppeteer-core cache of browsers then). This does not work with rules_js anymore, so we need to keep the cache local to the puppeteer postinstall script. This requires a little trickery right now to ensure resolution of the browsers at runtime works..

• server tests did miss the node types to be explicitly listed (as they would be in a fresh project), and this caused failures. Likely because we no longer patch resolution.

• avoid npm-module style imports from tests within the same package. This is not allowed with rules_js and also is inconsistent.

[alan-agius4]

LGTM, one NIT

[alan-agius4]

@devversion, this does not merge cleanly in the patch branch.