Ensure manifest.json version always matches the package.json

[zmofei]

This pull request improves the consistency and automation of version management between package.json and manifest.json, and enhances the developer workflow by updating pre-commit hooks and adding a test for version synchronization. The most important changes are grouped below:

Version Synchronization and Automation:

• Updated the syncManifestVersion script to check if the versions in package.json and manifest.json are already in sync before updating, and to log clear messages about the synchronization status.
• Added a pre-commit hook that automatically runs the version synchronization script and stages any changes to manifest.json before running linting, ensuring version consistency is enforced on every commit. (.husky/pre-commit, .husky/setup-hooks.js) [1] [2]

Testing and Validation:

• Added a new test (test/version-consistency.test.ts) to verify that the version fields in package.json and manifest.json always match.

Dependency and Metadata Updates:

• Bumped the version field in both package.json and manifest.json to 0.4.2 to reflect the latest release. [1] [2]

Code Quality:

• Updated Node.js import style in .husky/setup-hooks.js to use the node: prefix, aligning with modern Node.js best practices.

These changes help ensure that version mismatches are caught early, reduce manual steps for developers, and maintain a more reliable release process.