Require the addon directly instead of through bindings

The bindings package earns its place when an addon has to be found across
the several output directories node-gyp might have used. This addon is
built by cmake-rn to one known location, so a plain require says the same
thing with one less dependency — and it exercises the Babel plugin's
ordinary require path rather than its bindings special case.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013ugFE6vmMUVMTuoupvhMhX

Author: claude

packages/node-addon-examples/tests/module-register/addon.js

@@ -1,5 +1,7 @@
 const assert = require("assert");
-const addon = require("bindings")("addon.node");
+// cmake-rn emits to {targetSourceDir}/build/{configuration}, and this package's
+// build script pins the configuration.
+const addon = require("./build/RelWithDebInfo/addon.node");
 
 module.exports = () => {
   assert.strictEqual(addon.registration(), "napi_module_register");

packages/node-addon-examples/tests/module-register/package.json

@@ -3,8 +3,5 @@
   "version": "0.0.0",
   "description": "Tests of the deprecated napi_module_register registration",
   "main": "addon.js",
-  "private": true,
-  "dependencies": {
-    "bindings": "~1.5.0"
-  }
+  "private": true
 }