fix: resolve package import wildcard trailers

[cmpadden]

Summary

• resolve package.json import/export wildcard patterns that include a trailer, such as #*.js
• match both the pattern prefix and trailer before substituting the captured wildcard
• use Node-compatible pattern precedence and reject patterns containing multiple wildcards
• add an imports-wildcard trace fixture covering #internal/marker.js mapped through #*.js

Context

NFT previously recognized wildcard keys only when they ended in *. A valid import map such as:

{
  "imports": {
    "#*.js": "./dist/*.js"
  }
}

therefore failed to resolve #internal/marker.js. Consumers such as Nitro/nf3 would trace the package entry point but omit the internal target, producing an incomplete deployment artifact that failed at runtime with ERR_MODULE_NOT_FOUND.

Related reproduction and downstream workaround:

• https://github.com/cmpadden/eve-repro-nitro-wildcard-package-imports
• fix(eve): hosted tracing - include eve internal dependency closure eve#1181

Regression testing

The new test/unit/imports-wildcard fixture imports #internal/marker.js and expects dist/internal/marker.js in the trace.

Before this change, both the cwd-based and root-based fixture variants failed because the marker file was absent. After the resolver change, both variants pass.

Validation performed:

• pnpm build
• pnpm prettier-check
• pnpm exec jest test/unit.test.js --runInBand -t 'imports|exports-wildcard'
• pnpm exec jest --runInBand --silent — 1,475 tests passed