build(bazel): update bazel managed yarn to 1.13.0 (same as CI version)

[gregmagolan]

This PR updates bazel managed yarn.

Note: we tried using vendored_yarn previously but this caused major issues on Windows: bazelbuild/rules_nodejs#588

As a side note, CircleCI is currently on node 10.12 while Bazel is on node 10.9 which. We could update both to 10.13 at this point (node_repositories() has no definition for 10.12 and its not mirrored).

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]

the commit message mentions Node but the actual change is for yarn?

[alexeagle]

maybe add a comment that the principled answer is blocked on bazelbuild/rules_nodejs#588 ?

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