Don't manually set output jar timestamp

Setting the output jar timestamp to match the input jar confuses timestamp based build systems, and is unnecessary for bazel.

--
PiperOrigin-RevId: 147621642
MOS_MIGRATED_REVID=147621642

src/tools/android/java/com/google/devtools/build/android/desugar/Desugar.java

diff --git a/src/tools/android/java/com/google/devtools/build/android/desugar/Desugar.java b/src/tools/android/java/com/google/devtools/build/android/desugar/Desugar.java
index 9f927b5..5ac63e9 100644
--- a/src/tools/android/java/com/google/devtools/build/android/desugar/Desugar.java
+++ b/src/tools/android/java/com/google/devtools/build/android/desugar/Desugar.java
@@ -177,8 +177,6 @@
       Map<Path, LambdaInfo> leftBehind = lambdas.drain();
       checkState(leftBehind.isEmpty(), "Didn't process %s", leftBehind);
     }
-    // Use input's timestamp for output file so the output file is stable.
-    Files.setLastModifiedTime(options.outputJar, Files.getLastModifiedTime(options.inputJar));
   }
 
   private static void writeStoredEntry(ZipOutputStream out, String filename, byte[] content)