fix(runtime): suggest --allow-scripts for bindings native addon error (#34666)

## Problem

Importing an npm package that relies on a native addon (e.g.
`npm:libxmljs`, pulled in by `npm:xsd-validator`) fails with:

```
error: Uncaught (in promise) Error: Could not locate the bindings file. Tried:
 → .../node_modules/libxmljs/build/xmljs.node
 → .../node_modules/libxmljs/build/Release/xmljs.node
 ...
    at bindings (.../node_modules/bindings/bindings.js:96:9)
```

The compiled `.node` file is missing because the npm lifecycle (build)
scripts were not run. Deno already detects this situation and prints an
actionable hint ("…run `deno install --allow-scripts` to setup
`node_modules`"), but only for the Node-style `Cannot find module
'…/build/Release/xxx.node'` / `Require stack:` error.

The extremely common
[`bindings`](https://www.npmjs.com/package/bindings) npm package (used
by libxmljs and many other native addons) throws a *different* message —
`Could not locate the bindings file. Tried: …` — so the helpful
suggestion was never shown, leaving users stuck.

## Fix

Extend the native-addon error detection in
`get_suggestions_for_terminal_errors` to also match the `bindings`
package error message, so the same `--allow-scripts` / `nodeModulesDir`
hint is surfaced.

## Test

Added a spec test (`tests/specs/run/node_addon_bindings_suggestion`)
that reproduces the `bindings` error message and asserts the suggestion
is emitted.

Closes #27933

Closes denoland/divybot#396

Co-authored-by: divybot <divybot@users.noreply.github.com>
Co-authored-by: Divy Srivastava <me@littledivy.com>

Author: divybot

runtime/fmt_errors.rs

@@ -463,9 +463,18 @@ fn get_suggestions_for_terminal_errors(e: &JsError) -> Vec<FixSuggestion<'_>> {
     // - /.../deno/npm/registry.npmjs.org/canvas/2.11.2/lib/bindings.js
     // - /.../.cache/deno/npm/registry.npmjs.org/canvas/2.11.2/lib/canvas.js
     // ```
-    } else if msg.contains("Cannot find module")
+    // as well as errors thrown by the `bindings` npm package (used by
+    // libxmljs and many other native addons), like:
+    // ```
+    // Uncaught Error: Could not locate the bindings file. Tried:
+    //  → /.../node_modules/libxmljs/build/xmljs.node
+    //  → /.../node_modules/libxmljs/build/Release/xmljs.node
+    // ```
+    } else if (msg.contains("Cannot find module")
       && msg.contains("Require stack")
-      && msg.contains(".node'")
+      && msg.contains(".node'"))
+      || (msg.contains("Could not locate the bindings file")
+        && msg.contains(".node"))
     {
       return vec![
         FixSuggestion::info_multiline(&[

tests/specs/run/node_addon_bindings_suggestion/__test__.jsonc

@@ -0,0 +1,5 @@
+{
+  "args": "run main.js",
+  "output": "main.out",
+  "exitCode": 1
+}

tests/specs/run/node_addon_bindings_suggestion/main.js

@@ -0,0 +1,12 @@
+// Reproduces the error thrown by the `bindings` npm package (used by libxmljs
+// and many other native addons) when the compiled `.node` file is missing
+// because npm lifecycle scripts were not run. See denoland/deno#27933.
+const tried = [
+  "/node_modules/libxmljs/build/xmljs.node",
+  "/node_modules/libxmljs/build/Debug/xmljs.node",
+  "/node_modules/libxmljs/build/Release/xmljs.node",
+];
+throw new Error(
+  "Could not locate the bindings file. Tried:\n" +
+    tried.map((p) => " → " + p).join("\n"),
+);

tests/specs/run/node_addon_bindings_suggestion/main.out

@@ -0,0 +1,10 @@
+error: Uncaught (in promise) Error: Could not locate the bindings file. Tried:
+[WILDCARD]xmljs.node
+throw new Error(
+      ^
+    at file:///[WILDCARD]/main.js:9:7
+
+    info: Trying to execute an npm package using Node-API addons,
+          these packages require local `node_modules` directory to be present.
+    hint: Add `"nodeModulesDir": "auto" option to `deno.json`, and then run
+          `deno install --allow-scripts=npm:<package> --entrypoint <script>` to setup `node_modules` directory.