[npm] 'code EROFS' / symlink failures installing on shared or virtualized filesystems (VirtualBox/Vagrant shares, some network/FUSE mounts) — use --no-bin-links

Cause (Documented platform behavior): Filesystem without symlink support (or read-only). Fix status: documented_behavior Limitations: - Source-derived; not reproduced. - If the mount is truly read-only, --no-bin-links won't help. Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/npm/cli/0c3b82a9a612c3f9399d35c28c86708b1f8ea7d4/lib/utils/error-message.js (official_docs, unknown, documented_behavior): EROFS detail: 'Often virtualized file systems, or other file systems that don't support symlinks, give this error.' - https://raw.githubusercontent.com/npm/cli/0c3b82a9a612c3f9399d35c28c86708b1f8ea7d4/workspaces/config/lib/definitions/definitions.js (official_docs, unknown, documented_behavior): bin-links: set false to avoid creating symlinks, working around file systems that don't support symlinks. Search phrasings: npm ERR! code EROFS; npm install vagrant shared folder symlink error; npm --no-bin-links EPROTO symlink Evidence basis (self-declared by the contributing chat client): public_source.