Don't resolve symlinks for --sandbox_base

On macOS BigSur, the sandbox-exec command behaves slightly different than on
Catalina when firm links are present.

Resolving symlinks can prevent the sandbox for allowing write operations to the
sandbox base.

This effectively reverts a piece of 656a0ba, namely:

>  When using --experimental_sandbox_base, ensure that symlinks in the path are
>  resolved. Before this, you had to check whether on your system /dev/shm is a
>  symlink to /run/shm and then use that instead. Now it no longer matters, as
>  symlinks are resolved.

See bazelbuild#13766 for full details.

src/main/java/com/google/devtools/build/lib/sandbox/SandboxModule.java

@@ -125,8 +125,8 @@ private static Path computeSandboxBase(SandboxOptions options, CommandEnvironmen
               env.getRuntime().getProductName(),
               Fingerprint.getHexDigest(env.getOutputBase().toString()));
       FileSystem fileSystem = env.getRuntime().getFileSystem();
-      Path resolvedSandboxBase = fileSystem.getPath(options.sandboxBase).resolveSymbolicLinks();
-      return resolvedSandboxBase.getRelative(dirName);
+      // Don't resolve symlinks here: See https://github.com/bazelbuild/bazel/issues/13766
+      return fileSystem.getPath(options.sandboxBase).getRelative(dirName);
     }
   }