Note to reviewers: feat(@angular-devkit/build-optimizer): scrub ɵsetClassMetadata and ɵɵsetNgModuleScope calls is the main commit that, the others are smaller changes.

@vikerman suggested adding a e2e with lazy loaded chunk and track it on the size tracker to prevent regressions.

@filipesilva sgtm. I was going to add a similar e2e test to the angular repo as well. will this e2e test you intend to write be in the cli repo? I assume so. I guess it doesn't hurt to have this one in two places, but if you were to add the test just to the angular/angular repo then that would be fine as well.

For comparison, this is a new project with routing, before and after having a lazy route, and before this PR:

• without lazy routes

-rw-r--r-- 1 kamik 197609 214K Sep 25 13:09 main-es2015.js
-rw-r--r-- 1 kamik 197609 236K Sep 25 13:09 main-es5.js

• with lazy routes

-rw-r--r-- 1 kamik 197609  788 Sep 25 13:08 lazy-lazy-module-es2015.js
-rw-r--r-- 1 kamik 197609  788 Sep 25 13:08 lazy-lazy-module-es5.js
-rw-r--r-- 1 kamik 197609 301K Sep 25 13:08 main-es2015.js
-rw-r--r-- 1 kamik 197609 325K Sep 25 13:08 main-es5.js

• with lazy routes, after this PR

-rw-r--r-- 1 kamik 197609  772 Sep 25 14:14 lazy-lazy-module-es2015.js
-rw-r--r-- 1 kamik 197609  772 Sep 25 14:14 lazy-lazy-module-es5.js
-rw-r--r-- 1 kamik 197609 258K Sep 25 14:14 main-es2015.js
-rw-r--r-- 1 kamik 197609 282K Sep 25 14:14 main-es5.js

Note to caretaker: it is expected that the ci/angular: size check increases in size, as now we're tracking a new project with lazy routes, which also includes the router.

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