[Feature] - Support for node --conditions flag in subpath imports

[owenallenaz]

• I'd be willing to implement this feature (contributing guide)
• This feature is important to have in this repository; a contrib plugin wouldn't do

Describe the user story

A package can contain subpath imports as declared here.

Then I should be able to require that content via: const something = require("#hax");. That syntax there works just fine, but not if you specify the node cli option --conditions. For example, I should be able to declare:

imports: {
   "#hax": {
     "development": "./src/hax.js",
     "default": "./src/hax_default.js"
   }
}

hax.js

exports.test = function() {
    console.log("called");
}

hax_default.js

exports.test = function() {
    console.log("hax_default called");
}

test.js

const { test } = require("#hax");

test();

Using the setup above if I execute:

: node test.js
hax_default called (CORRECT)
: node --conditions development test.js
called (CORRECT)
: yarn node test.js
hax_default called (CORRECT)
: yarn node --conditions development test.js
hax_default called (WRONG!)

This indicates that the yarn berry loader isn't properly utilizing the --conditions flag of Node.

Tested on:
node: v16.18.0
yarn: 3.2.4

This does not happen if I utilize nodeLinker: "node-modules". It works correctly in that situation.