Add pre-merge check for non-locked packages (Fixes #50604)

[harshasiddartha]

Description

This PR adds a pre-merge check to ensure that all packages in package.json files use specific versions instead of range specifiers (^, ~, >=, <=, >, <, *, x, latest, etc.).

Changes

• ✅ Added scripts/check-package-versions.js script that:

  • Scans all package.json files in the repository
  • Checks dependencies, devDependencies, peerDependencies, and optionalDependencies
  • Detects range specifiers and reports violations
  • Provides warnings for engines field (which typically allows ranges)

• ✅ Added check-package-versions script to package.json scripts section

• ✅ Added GitHub Actions workflow job checkPackageVersions to .github/workflows/pull_request.yml:

  • Runs on PR open, reopen, and synchronize events
  • Fails the CI if any package.json files contain range specifiers
  • Uses Node.js 24 (matching the project's engine requirement)

Testing

• ✅ Script successfully validates existing package.json files
• ✅ Current package.json already uses specific versions (chalk: 4.1.2)
• ✅ Script correctly identifies range specifiers when tested

Related Issue

Fixes #50604

Checklist

• Code follows the project's style guidelines
• Tests have been added/updated
• Documentation has been updated (if needed)
• All existing tests pass
• No new warnings introduced

[diracdeltas]

@mihaiplesa PTAL as i think you may have started working on this

[mihaiplesa]

@harshasiddartha thank you for the contribution but we've chosen a different approach so closing this.