fix(dsn): ignore EINVAL from readdirSync on special files (#1286)

When the DSN code scanner walks directories, `readdirSync` can encounter
special filesystem entries (e.g., `/proc` paths on Linux). For these
entries, `readdirSync` (via `scandir`) can throw an `EINVAL` error.

Previously, `EINVAL` was not included in the list of ignorable
filesystem errors in `src/lib/dsn/fs-utils.ts::isIgnorableFileError`.
This led to these benign and expected errors being captured as Sentry
issues (CLI-2AW).

This change adds `EINVAL` to the set of ignorable errors in
`isIgnorableFileError` and updates the corresponding JSDoc comment. This
suppresses the spurious Sentry reports without altering the directory
walker's behavior, as it already correctly handles these cases by
returning an empty list of entries.

Fixes
[CLI-2AW](https://sentry.sentry.io/issues/7627608153/?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

@@ -17,6 +17,7 @@ import * as Sentry from "@sentry/node-core/light";
  * - EPERM: Operation not permitted (e.g., file locked, or system-level restriction)
  * - 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)
  *
  * All other errors are unexpected and should be reported to Sentry.
  *
@@ -31,7 +32,8 @@ function isIgnorableFileError(error: unknown): boolean {
       code === "EACCES" ||
       code === "EPERM" ||
       code === "EISDIR" ||
-      code === "ENOTDIR"
+      code === "ENOTDIR" ||
+      code === "EINVAL"
     );
   }
   return false;