fix: don't let rimraf failure prevent EPERM/EBUSY retry loop

On Windows, when the target file is locked (e.g. by antivirus or
another process), both rename and rimraf fail with EPERM. Previously
rimraf threw before the retry loop was reached. Now rimraf errors are
swallowed so the retry loop can wait for the lock to clear.

Author: zkochan

rename-overwrite/index.js

@@ -30,7 +30,7 @@ export async function renameOverwrite (oldPath, newPath, retry = 0) {
       case 'EPERM':
       case 'EACCESS':
       case 'EBUSY': {
-        await rimraf(newPath)
+        try { await rimraf(newPath) } catch {}
         const start = Date.now()
         let backoff = 0
         let lastError = err
@@ -89,7 +89,7 @@ export function renameOverwriteSync (oldPath, newPath, retry = 0) {
       case 'EPERM':
       case 'EACCESS':
       case 'EBUSY': {
-        rimrafSync(newPath)
+        try { rimrafSync(newPath) } catch {}
         const start = Date.now()
         let backoff = 0
         let lastError = err