Always run ProcessClosurePrimitives before module rewriting

Only affects builds enabling the legacy "rewrite modules before typechecking" mode. I don't expect this to be a breaking change.

Reasoning: we eventually want module rewriting to run post-typechecking for every build, but ProcessClosurePrimitives will still need to run pre-typechecking. This change gets us closer to that ideal pass ordering.
PiperOrigin-RevId: 618922256

Author: lauraharker

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

@@ -234,8 +234,8 @@ protected PassListBuilder getChecks() {
       checks.maybeAdd(checkSideEffects);
       checks.maybeAdd(angularPass);
       checks.maybeAdd(closureGoogScopeAliases);
-      addModuleRewritingPasses(checks, options);
       checks.maybeAdd(closurePrimitives);
+      addModuleRewritingPasses(checks, options);
       checks.maybeAdd(clearTypedScopeCreatorPass);
       checks.maybeAdd(clearTopTypedScopePass);
       checks.maybeAdd(generateExports);
@@ -344,15 +344,15 @@ protected PassListBuilder getChecks() {
       checks.maybeAdd(closureGoogScopeAliases);
     }
 
+    if (options.closurePass) {
+      checks.maybeAdd(closurePrimitives);
+    }
+
     // TODO(b/141389184): Move this after the Polymer pass
     if (options.shouldRewriteModulesBeforeTypechecking()) {
       addModuleRewritingPasses(checks, options);
     }
 
-    if (options.closurePass) {
-      checks.maybeAdd(closurePrimitives);
-    }
-
     // It's important that the PolymerPass run *after* the ClosurePrimitives and ChromePass rewrites
     // and *before* the suspicious code checks. This is enforced in the assertValidOrder method.
     if (options.polymerVersion != null) {