Move type removal to happen just after ambiguation

The only type-based optimizations that occur after ambiguation are inside
PeepholeFoldConstants and PeepholeReplaceKnownMethods when run as part of the
"late" peephole optmizations.
Since these also run before ambiguation as part of the normal+early peephole
passes, those type-based optimizations will have already had the opportunity to
run, and thus removing the types from only the "late" version of this pass
likely has negligible, if any, effect on code size.

PiperOrigin-RevId: 321667491

Author: blickly

src/com/google/javascript/jscomp/DefaultPassConfig.java

@@ -799,6 +799,8 @@ protected List<PassFactory> getOptimizations() {
       passes.add(ambiguateProperties);
     }
 
+    passes.add(removeTypes);
+
     if (options.propertyRenaming == PropertyRenamingPolicy.ALL_UNQUOTED) {
       passes.add(renameProperties);
     }
@@ -871,8 +873,6 @@ protected List<PassFactory> getOptimizations() {
       passes.add(latePeepholeOptimizations);
     }
 
-    passes.add(removeTypes);
-
     if (options.anonymousFunctionNaming == AnonymousFunctionNamingPolicy.UNMAPPED) {
       passes.add(nameUnmappedAnonymousFunctions);
     }