build: remove windows runfile workaround

[devversion]

• Since bazel-contrib/rules_nodejs@1f97eb6 landed, we can safely remove the workaround by updating the NodeJS and TypeScript Bazel rules.
• Also we are creating our own getFileContent testing method because it's not guaranteed that the internal testing utilities from @schematics/angular always stay the same. Additionally this works around an issue where test folders are excluded in the Bazel managed deps by default.

Blocked on angular/angular#27138 being merged.

[jelbourn]

LGTM

[gregmagolan]

Just a note that rules_nodejs 0.16.1 won't work with material but the latest commit will (symlink issue fixed by bazel-contrib/rules_nodejs#422). This was due to the test folder being filtered out that was needed in the @schematics/angular package.

You can either update this PR to that commit or Alex should tag 0.16.2 shortly.

With the rules_nodejs update, the update to yarn 1.10+ is possible as well which supports the integrity field:

node_repositories(
  # For deterministic builds, specify explicit NodeJS and Yarn versions.
  node_version = "10.10.0",
  # Use latest yarn version to support integrity field (added in yarn 1.10)
  yarn_version = "1.12.1",
)

[devversion]

Rebased. This is ready now.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}