Sort package.json dependencies alphabetically

[diegomais]

Description

This PR adds alphabetical sorting for dependencies and devDependencies in the generated package.json file. The sorting uses simple string comparison to match the behavior of npm, yarn, and pnpm package managers.

Changes

• Added sorting for both dependencies and devDependencies sections
• Used basic string comparison (< and > operators)
• Maintains consistent ordering across different package managers

Testing

To verify this change:

1. Create a new Next.js project with various dependencies:

   pnpm create next-app test-app --typescript --tailwind --eslint

2. Check the generated package.json file to ensure:
   • Dependencies are sorted alphabetically
   • DevDependencies are sorted alphabetically
   • The order matches what you'd see after running pnpm install
3. Verify that the installation process works correctly with the sorted dependencies

Impact

This change improves the consistency of generated package.json files and makes them more predictable across different package managers. It's a small but useful improvement for maintainability and readability.

[ijjk]

Allow CI Workflow Run

• approve CI run for commit: 7083a79

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

[diegomais]

Before this change, package managers would reorder dependencies in package.json after installation, causing unnecessary git diffs like this:

This was problematic because:

• It created noise in git history
• Made it harder to review actual dependency changes
• Caused unnecessary merge conflicts
• Required manual sorting to maintain consistency

Now the dependencies are pre-sorted in the same way package managers would sort them, preventing these unnecessary changes from being committed.