build: remove tsickle from compiler-cli deps

[alexeagle]

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

[mary-poppins]

You can preview 93085dd at https://pr25649-93085dd.ngbuilds.io/.

[mary-poppins]

You can preview e36d92f at https://pr25649-e36d92f.ngbuilds.io/.

[mary-poppins]

You can preview 0fbe9dd at https://pr25649-0fbe9dd.ngbuilds.io/.

[mary-poppins]

You can preview d6dfdc9 at https://pr25649-d6dfdc9.ngbuilds.io/.

[mary-poppins]

You can preview 363339b at https://pr25649-363339b.ngbuilds.io/.

[alxhub]

Code-wise, this LGTM.

I'm pondering the larger implications, though. Historically the interaction between tsickle and compiler-cli has caused issues in a few places, and this tends to be much worse in Ivy where the AST we feed tsickle can be noticeably changed from the original source code. Tsickle does much of its work using the original source text.

I'm wary that removing tsickle as a step in our tests will introduce bugs which only show up at g3sync time. Then again, most of our tests run without annotateForClosureCompiler enabled anyway, so maybe this isn't a new concern.

Thoughts?

[alexeagle]

We have the integration/hello-world-closure test which is the best place for us to locally catch gross regressions of using closure.

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