feat(pack): support publishConfig.type

[cometkim]

What's the problem this PR addresses?

This PR allows overriding the "type" field on the manifest when packing a package.

{
  "main": "./src/index.ts",
  "publishConfig": {
    "type": "module",
    "main": "./lib/index.js"
  }
}

I wanna build an ESM-first package, but at the same time, I still wanna implicitly load packages with legacy Node resolution in my dev environment to interop with TypeScript which don't yet fully support Node ESM resolution

...

How did you fix it?

by supporting overriding "type" with "publishConfig" object

...

Checklist

• I have read the Contributing Guide.

• I have set the packages that need to be released for my changes to be effective.

• I will check that all automated PR checks pass before the PR gets reviewed.

[merceyz]

Could you add a test to https://github.com/yarnpkg/berry/blob/f2513070530f4d309e3b398170a0d13865c104a8/packages/acceptance-tests/pkg-tests-specs/sources/commands/pack.test.js?

[arcanis]

I think the right field is types (or typings, but better only support one), not type 🤔

[merceyz]

@arcanis type is the correct field in this case https://nodejs.org/dist/latest-v16.x/docs/api/packages.html#type

[arcanis]

Of course, my bad 🤦‍♀️

[arcanis]

Sorry for the delay @cometkim 🙏