Support dirfd relative iops on Windows

We always favor calling functions like openat(), fstatat(), etc. because
Linux, XNU, FreeBSD, and OpenBSD all elected to support them, while some
systems like Android love them so much, that they stopped supporting the
old interfaces.

This change ensures that when dirfd is actually a dirfd and not AT_FDCWD
we'll do the right thing on Windows NT. We use an API that's been around
since Vista to accomplish that.

This change also adds exponential backoff to chdir() on Windows since it
seems almost as flaky on Windows 7 as the rmdir() function.

libc/calls/access.c

@@ -17,10 +17,7 @@
 │ PERFORMANCE OF THIS SOFTWARE.                                                │
 ╚─────────────────────────────────────────────────────────────────────────────*/
 #include "libc/calls/calls.h"
-#include "libc/calls/internal.h"
-#include "libc/dce.h"
 #include "libc/sysv/consts/at.h"
-#include "libc/sysv/errfuns.h"
 
 /**
  * Checks if effective user can access path in particular ways.
@@ -31,12 +28,5 @@
  * @asyncsignalsafe
  */
 int access(const char *path, int mode) {
-  char16_t path16[PATH_MAX];
-  if (!path) return efault();
-  if (!IsWindows()) {
-    return faccessat$sysv(AT_FDCWD, path, mode, 0);
-  } else {
-    if (__mkntpath(path, path16) == -1) return -1;
-    return ntaccesscheck(path16, mode);
-  }
+  return faccessat(AT_FDCWD, path, mode, 0);
 }