fix(lib/node): change ERR_INVALID_PACKAGE_TARGET to ERR_PACKAGE_PATH_NOT_EXPORTED when no package.json#exports condition matches

[sgasho]

related: #29374

The error message changed from ERR_INVALID_PACKAGE_TARGET to ERR_PACKAGE_PATH_NOT_EXPORTED when no package.json#exports condition matched.
Node.js uses the same error message in this situation.

There might be a more appropriate error message, but for now, I've matched the default behavior of Node.js.

Supplements

Why just removing InvalidPackageTargetError at resolve_package_target_inner leads to PackagePathNotExportedError is that Ok(None) from resolve_package_target_inner will be passed to resolve_package_target -> package_exports_resolve_internal then package_exports_resolve_internal considers None as a PackagePathNotExportError

package_exports_resolve_internal

        let resolved = self.resolve_package_target(
          package_json_path,
          target,
          "",
          package_subpath,
          maybe_referrer,
          resolution_mode,
          false,
          false,
          conditions,
          resolution_kind,
        )?;
        return match resolved {
          Some(resolved) => Ok(resolved),
          None => Err(
            PackagePathNotExportedError {
              pkg_json_path: package_json_path.to_path_buf(),
              subpath: package_subpath.to_string(),
              maybe_referrer: maybe_referrer.map(|r| r.display()),
              resolution_kind,
            }
            .into(),
          ),
        };

Screenshots

Before

After

reference: node.js