fix(fs): ignore ELOOP errors during file scanning (#1320)

Previously, `ELOOP` errors (too many symbolic links encountered, often
due to cyclic symlinks) were being reported to Sentry when the CLI
scanned for files like `.env.local`.

The `isIgnorableFileError` function in `src/lib/dsn/fs-utils.ts` did not
include `ELOOP` in its allowlist of file system errors that should be
silently ignored. This led to noisy Sentry captures for expected
filesystem conditions.

This change adds `ELOOP` to the list of ignorable error codes in
`isIgnorableFileError` and updates the corresponding JSDoc, ensuring
these errors are now correctly handled and not reported.

Fixes
[CLI-2CK](https://sentry.sentry.io/issues/7642577038/?seerDrawer=true)

<sub>Comment `@sentry <feedback>` on this PR to have Autofix iterate on
the changes.</sub>

Co-authored-by: sentry[bot] <39604003+sentry[bot]@users.noreply.github.com>

Author: sentry[bot]

src/lib/dsn/fs-utils.ts

@@ -18,6 +18,7 @@ import * as Sentry from "@sentry/node-core/light";
  * - EISDIR: Path is a directory, not a file (e.g., `.env/` directory instead of `.env` file)
  * - ENOTDIR: A path component is not a directory (e.g., `/file.txt/child`)
  * - EINVAL: Invalid argument (e.g., scandir on a special/virtual filesystem entry like /proc paths)
+ * - ELOOP: Too many symbolic links (e.g., cyclic symlink encountered during scan)
  *
  * All other errors are unexpected and should be reported to Sentry.
  *
@@ -33,7 +34,8 @@ function isIgnorableFileError(error: unknown): boolean {
       code === "EPERM" ||
       code === "EISDIR" ||
       code === "ENOTDIR" ||
-      code === "EINVAL"
+      code === "EINVAL" ||
+      code === "ELOOP"
     );
   }
   return false;