fix(rename-overwrite): handle EBUSY error code

[anthochamp]

When using rename-overwrite in Windows, EBUSY might be raised by the underlying OS which should trigger a retry the same way it is done for EACCESS/EPERM.

Context:

We're using pnpm on a large project and getting EBUSY error on CI (GitLab, Windows Server runners).

We traced back the problem to the call to renameOverwrite from the sync or async versions of forceSymlink in the symlink-dir library.

A similar issue has already been solved in pnpm.

[Gadzy]

@zkochan Thanks for accepting my @anthochamp's PR.
I can see that you published a patch version 6.0.3 of rename-overwrite – now available in pnpm 10.11.1 if I'm correct – but there's no mention of it in the CHANGELOG. Any reason why?