test: remove bluebird remnants from test fixture

The test fixture in test/fixtures/bluebird was largely copied from
bluebird, where a regression in Node.js was discovered. Simplify the
test by removing a lot of things that aren't necessary to replicate the
problem. Change name from bluebird to something less likely to cause
someone to believe that we are actually loading bluebird (as we are
not).

PR-URL: #31435
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: David Carlier <[email protected]>

test/fixtures/package-main-enoent/package.json

@@ -0,0 +1,4 @@
+{
+  "name": "package-main-enoent",
+  "main": "./fhqwhgads.js"
+}

test/fixtures/package-main-enoent/test.js

@@ -0,0 +1,8 @@
+'use strict';
+
+// The path in "main" in "package.json" does not exist here, but it does in
+// the copy in node_modules. This is being tested because bluebird tests depend
+// on this behavior and it was accidentally broken by a seemingly unrelated
+// commit on master.
+
+require('package-main-enoent');

test/parallel/test-require-invalid-main-no-exports.js

@@ -13,8 +13,9 @@ const assert = require('assert');
 const { spawnSync } = require('child_process');
 const fixtures = require('../common/fixtures');
 
-const { error, status, stderr } =
-  spawnSync(process.execPath, [fixtures.path('bluebird', 'test.js')]);
+const testFile = fixtures.path('package-main-enoent', 'test.js');
+
+const { error, status, stderr } = spawnSync(process.execPath, [testFile]);
 
 assert.ifError(error);
 assert.strictEqual(status, 0, stderr);