fix(cli): suppress esbuild warnings in CLI build

Fixed two esbuild warnings:
1. commonjs-variable-in-esm - Intentional CommonJS compatibility code
2. require-resolve-not-external - node-gyp marked as external

Changes:
- Added node-gyp to external array (for runtime require.resolve)
- Added logOverride to silence commonjs-variable-in-esm warning

The CommonJS exports in config.mts and flags.mts are intentional for
compatibility when files are require()'d at runtime. The warnings
were harmless but noisy.

node-gyp must be external because getNmNodeGypPath() uses
require.resolve('node-gyp/package.json') to locate the user's
installed node-gyp at runtime, not bundle it.

Author: jdalton

packages/cli/.config/esbuild.cli.build.mjs

@@ -110,7 +110,14 @@ const config = {
   // With platform: 'node', esbuild automatically externalizes all Node.js
   // built-ins. The explicit external array with builtinModules is redundant
   // (but doesn't hurt as extra safety).
-  external: [],
+  external: [
+    'node-gyp', // Required for require.resolve('node-gyp/package.json')
+  ],
+
+  // Suppress warnings for intentional CommonJS compatibility code.
+  logOverride: {
+    'commonjs-variable-in-esm': 'silent',
+  },
 
   // Add shebang.
   banner: {