fix: deep-sort publishConfig with the same field order as package.json

[Boshen]

Summary

• Closes publishConfig should be ordered with the same order of main package.json #71.
• publishConfig now recurses through sort_object_keys, so its fields follow the canonical package.json order (e.g. name → main → types → dependencies → unknown fields alphabetically) instead of a flat alphabetical sort.
• Fixture and snapshot expanded to exercise the new behavior with name, main, types, tag, and a nested dependencies.

🤖 Generated with Claude Code

[codspeed-hq]

Merging this PR will degrade performance by 4.98%

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

❌ 2 regressed benchmarks
✅ 2 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Benchmark	BASE	HEAD	Efficiency
❌	sort already sorted package.json	174.7 µs	183.1 µs	-4.56%
❌	sort small package.json	177.2 µs	186.5 µs	-4.98%

---

_{Comparing fix/publish-config-deep-sort (2a24bfa) with main (a8840ff)}