Move retry logic to where it's being used.

Simple refactoring that moves the retry logic from the
RemoteModule to the RemoteSpawnRunner where it's actually
being used.

Closes #10212.

PiperOrigin-RevId: 279938161
diff --git a/src/test/java/com/google/devtools/build/lib/remote/RemoteSpawnRunnerTest.java b/src/test/java/com/google/devtools/build/lib/remote/RemoteSpawnRunnerTest.java
index 79c4380..c8eb2e8 100644
--- a/src/test/java/com/google/devtools/build/lib/remote/RemoteSpawnRunnerTest.java
+++ b/src/test/java/com/google/devtools/build/lib/remote/RemoteSpawnRunnerTest.java
@@ -112,7 +112,6 @@
   private FileOutErr outErr;
 
   private RemoteOptions remoteOptions;
-  private RemoteRetrier retrier;
 
   @Mock private RemoteExecutionCache cache;
 
@@ -146,7 +145,6 @@
     outErr = new FileOutErr(stdout, stderr);
 
     remoteOptions = Options.getDefaults(RemoteOptions.class);
-    retrier = RemoteModule.createExecuteRetrier(remoteOptions, retryService);
   }
 
   @AfterClass
@@ -817,7 +815,7 @@
             "command-id",
             cache,
             executor,
-            retrier,
+            retryService,
             digestUtil,
             logDir,
             /* filesToDownload= */ ImmutableSet.of());
@@ -1014,7 +1012,7 @@
         "command-id",
         cache,
         executor,
-        retrier,
+        retryService,
         digestUtil,
         logDir,
         topLevelOutputs);