rm: use "traversal failed" message when readdir fails during recursive removal

When readdir fails mid-traversal (e.g., due to I/O errors), GNU rm
reports "traversal failed: <dir>" rather than "cannot remove '<dir>'".
Update the error handling in safe_remove_dir_recursive_impl to match
this behavior.

Fixes GNU test: tests/rm/rm-readdir-fail.sh

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: kevinburkesegment

src/uu/rm/locales/en-US.ftl

@@ -44,6 +44,7 @@ rm-error-dangerous-recursive-operation-same-as-root = it is dangerous to operate
 rm-error-use-no-preserve-root = use --no-preserve-root to override this failsafe
 rm-error-refusing-to-remove-directory = refusing to remove '.' or '..' directory: skipping {$path}
 rm-error-cannot-remove = cannot remove {$file}
+rm-error-traversal-failed = traversal failed: {$path}
 rm-error-may-not-abbreviate-no-preserve-root = you may not abbreviate the --no-preserve-root option
 
 # Verbose messages

src/uu/rm/locales/fr-FR.ftl

@@ -44,6 +44,7 @@ rm-error-dangerous-recursive-operation-same-as-root = il est dangereux d'opérer
 rm-error-use-no-preserve-root = utilisez --no-preserve-root pour outrepasser cette protection
 rm-error-refusing-to-remove-directory = refus de supprimer le répertoire '.' ou '..' : ignorer {$path}
 rm-error-cannot-remove = impossible de supprimer {$file}
+rm-error-traversal-failed = échec du parcours : {$path}
 rm-error-may-not-abbreviate-no-preserve-root = Vous ne pouvez pas abréger l'option --no-preserve-root
 
 # Messages verbeux

src/uu/rm/src/platform/unix.rs

@@ -349,7 +349,11 @@ pub fn safe_remove_dir_recursive_impl(path: &Path, dir_fd: &DirFd, options: &Opt
             return !options.force;
         }
         Err(e) => {
-            return handle_error_with_force(e, path, options);
+            let e = e.map_err_context(|| {
+                translate!("rm-error-traversal-failed", "path" => path.display().to_string())
+            });
+            show_error!("{e}");
+            return true;
         }
     };