fix(release): support npm 12 publish output

[omegent-app]

Why

The release runner uses npm 12. Its npm pack --json output is keyed by package name, and duplicate-publish E403 responses put their text in error.message. The release tooling only handled npm 11 and earlier shapes.

What

Accept npm pack metadata returned as an array, a direct object, or a package-name-keyed object. Recognize duplicate-publish errors from npm's summary, detail, or message.

How

The staged package remains validated by requiring a files array after normalization. Changesets still skips only errors containing the known duplicate-version message.

Remarks

Verified with npm 12.0.2 against the core effect-app package and with a forced frozen pnpm install.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[pkg-pr-new]

Open in StackBlitz

@effect-app/cli

npm i https://pkg.pr.new/effect-app/libs/@effect-app/cli@840

effect-app

npm i https://pkg.pr.new/effect-app/libs/effect-app@840

@effect-app/eslint-codegen-model

npm i https://pkg.pr.new/effect-app/libs/@effect-app/eslint-codegen-model@840

@effect-app/eslint-shared-config

npm i https://pkg.pr.new/effect-app/libs/@effect-app/eslint-shared-config@840

@effect-app/infra

npm i https://pkg.pr.new/effect-app/libs/@effect-app/infra@840

@effect-app/vue

npm i https://pkg.pr.new/effect-app/libs/@effect-app/vue@840

@effect-app/vue-components

npm i https://pkg.pr.new/effect-app/libs/@effect-app/vue-components@840

commit: e6edd2c