fix: automatically trace package aliases from package.json

[kricsleo]

🔗 Linked issue

resolves #3034

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This PR automatically adds package aliases from package.json for tracing, so the final bundle can correctly link these dependencies.

For example:

"dependencies": {
  "@std/ulid": "npm:@jsr/[email protected]",
  "lodash4": "npm:[email protected]"
}

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[pi0]

This is not a reliable way.

• Aliases can be done using resolutions, overrides, or aliases like this
• Rules can also be from workspace settings
• Package aliases can happen at any nested level and are respected by package managers.

[kricsleo]

I see, then what about adding package aliases here:

nitro/src/build/plugins/externals.ts

Lines 137 to 139 in 32e1850

	// Normally package name should be same as originalId
	// Edge cases: Subpath export and full paths
	if (pkgName !== originalId) {

If the imported package name doesn't match the resolved package name (also considering "Subpath export and full paths"), then there might be a package alias. We could automatically add this alias to traceAlias. How does that sound? 🤔