Rename requireNodeAddon to dlopen?

[kraenhansen]

In Node.js there's a couple of API you can use to initialize a Node-API addon:

1. process.dlopen({ export: {} }, "./foo")
2. require("./foo")
3. process._linkedBinding("foo") to load Node-API addons statically linked into the executable and registered on startup.

It turns out process.dlopen doesn't actually require an absolute or relative file path, when given a filename it will attempt to load a system-level dynamic library using a couple of candidate paths, much like what we want to do in our requireNodeAddon implementation.

process.dlopen({ exports: {} }, "foo")
Uncaught:
[Error: dlopen(foo, 0x0001): tried: 'foo' (no such file), '/System/Volumes/Preboot/Cryptexes/OSfoo' (no such file), '/usr/lib/foo' (no such file, not in dyld cache), 'foo' (no such file)] {
  code: 'ERR_DLOPEN_FAILED'
}

Would we want to converge some of the naming here? I mean, we'd likely not want to overload require and we probably also wouldn't like to provide a process global, but perhaps we want to export dlopen and / or linkedBinding from the host package?