build: remove obsolete Bazel function ctx.new_file

[kyliau]

This is a resurrection of #37759
I made a mistake in git push and accidentally closed the PR.

The function was removed by default in Bazel 0.27.
It is still accessible with the flag --incompatible_new_actions_api
(which is set in Google code base), but the flag will be deleted very soon.

This change should be a no-op for Bazel users. The change was tested in
Google (cl/318277076) and should be safe as well.

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• angular.io application / infrastructure changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

[kyliau]

presubmit: https://test.corp.google.com/OCL:321387731:BASE:321388014:1594834212242:616f8f4f

[dgp1130]

Since this is the same as the previous PR, you can probably just force successful presubmit and link to the old ID rather than running a new one.

[kyliau]

cc: @laurentlb this is good to go, thank you!

[AndrewKushnir]

FYI, I had to rollback this change due to the issues in Google's codebase (see PR #38101), so I'me reopening this PR.

[petebacondarwin]

@AndrewKushnir - what are the next steps for this PR?

[AndrewKushnir]

Hey @petebacondarwin, thanks for the note.
I believe the next step is to test the changes in g3 again (and run a global TAP to verify)...

@kyliau @dgp1130 do you plan to look into this or should we close the PR for now?

[laurentlb]

I think this can be reverted until someone picks up the cleanup work in google3 (cc @lberki).

[kyliau]

The cleanup work mentioned by @laurentlb is tracked in b/160134064. Meanwhile I'll close this.

[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.}