windows: fix flaky bunx test

[nektro]

during extract_tarball, when ENOTEMPTY is received on windows the current behavior is to delete the target folder and try again. however when many instances are racing that are all installing the same dependency one of the other instances may write to the cache before the current one can; thus throwing ENOTEMPTY yet again. it is then better to notice this and move on to the next entry.

[github-actions]

❌ @nektro, your commit has failing tests :(

💪 2 failing tests Darwin AARCH64

• test/js/bun/http/serve.test.ts 1 failing
• test/js/node/http2/node-http2.test.js 1 failing

💻 1 failing tests Darwin x64 baseline

• test/js/web/workers/worker.test.ts 1 failing

💻 2 failing tests Darwin x64

• test/cli/install/registry/bun-install-registry.test.ts 2 failing
• test/js/bun/test/test-test.test.ts 1 failing

🐧💪 1 failing tests Linux AARCH64

• test/integration/mysql2/mysql2.test.ts 6 failing

🐧🖥 1 failing tests Linux x64

• test/js/node/child_process/child_process-node.test.js 1 failing

🪟💻 7 failing tests Windows x64 baseline

• test/cli/install/migration/migrate.test.ts 1 failing
• test/integration/esbuild/esbuild.test.ts 1 failing
• test/integration/next-pages/test/dev-server-ssr-100.test.ts 1 failing
• test/integration/next-pages/test/dev-server.test.ts 1 failing
• test/integration/next-pages/test/next-build.test.ts 1 failing
• test/js/bun/shell/bunshell.test.ts 1 failing
• test/js/node/dns/node-dns.test.js 2 failing

🪟💻 8 failing tests Windows x64

• test/cli/install/registry/bun-install-registry.test.ts SIGTERM
• test/integration/esbuild/esbuild.test.ts 1 failing
• test/integration/next-pages/test/dev-server-ssr-100.test.ts 1 failing
• test/integration/next-pages/test/dev-server.test.ts 1 failing
• test/integration/next-pages/test/next-build.test.ts 1 failing
• test/js/bun/shell/bunshell.test.ts 1 failing
• test/js/bun/shell/commands/rm.test.ts 1 failing
• test/js/node/dns/node-dns.test.js 2 failing

View logs