[DOCS] package.json#repository should clarify normalization steps and future plans.

[JoshuaKGoldberg]

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

My repo's package.json file has a "repository" field set to "JoshuaKGoldberg/emojipedia" as a shorthand. npm publish still works, but gives this complaint:

ERROR npm WARN publish npm auto-corrected some errors in your package.json when publishing.  Please run "npm pkg fix" to address these errors.
npm WARN publish errors corrected:
npm WARN publish "repository" was changed from a string to an object
npm WARN publish "repository.url" was normalized to "git+https://github.com/JoshuaKGoldberg/emojipedia.git"

https://github.com/JoshuaKGoldberg/emojipedia/blob/7b67fe1986852fb271c2eab59fe536ee3476322f/package.json#L5

Expected Behavior

Per npm/npm#3783 -> https://docs.npmjs.com/cli/v10/configuring-npm/package-json#repository, using a repository shorthand like "JoshuaKGoldberg/emojipedia" should be allowed.

Steps To Reproduce

1. Create a project whose package.json's "repository" value is a GitHub string shorthand
2. npm publish

Environment

• npm: 10.2.4 and 10.5.0
• Node.js: v20.11.0
• OS Name: macOS
• System Model Name: Mac Studio
• npm config:

//registry.npmjs.org/:_authToken = (protected) 
provenance = true

[wraithgar]

Historically npm has normalized that entry when publishing a package, which lead to a discrepancy between what was in the package.json and what was in the manifest on the registry. This warning is showing that change happening. At some point in the future we are hoping to stop allowing those fields to differ, so the warning is letting folks clean things up now.

The docs will likely need to be updated on this to reflect the new reality.