Fix log printing to correctly associate comp steps and numPackages wi…

…th the

right log lines.  The variables for numLoadedPackages and computationSteps were
transposed in the logging logic.

PiperOrigin-RevId: 327143590

src/main/java/com/google/devtools/build/lib/packages/metrics/ExtremaPackageMetricsRecorder.java

@@ -129,11 +129,11 @@ public synchronized void loadingFinished() {
         c -> Durations.toMillis(c.getPackageMetricsInternal().getLoadDuration()));
     logIfNonEmpty(
         "Largest packages (num targets)",
-        packagesWithMostComputationSteps.getExtremeElements(),
+        largestPackages.getExtremeElements(),
         c -> c.getPackageMetricsInternal().getNumTargets());
     logIfNonEmpty(
         "Packages with most computation steps",
-        largestPackages.getExtremeElements(),
+        packagesWithMostComputationSteps.getExtremeElements(),
         c -> c.getPackageMetricsInternal().getComputationSteps());
     logIfNonEmpty(
         "Packages with most transitive loads (num bzl files)",