fix: node path import

[zhongliang02]

This PR addresses an issue with the path validator introduced in versions 1.2.3 to 1.2.7 of our package. The node:path import syntax, while explicitly pointing to a Node.js built-in module, is not supported by the Next.js webpack configuration, causing build failures in some projects.

Changes:

• Removed node: prefix from fs and path import statements

Rationale:

1. This change resolves build failures in Next.js projects
2. Security concerns about package squatting are mitigated:
   • Node.js preferentially loads built-in modules like fs and path even without the node: prefix.
   • Node.js module resolution algorithm prioritises built-in modules over similarly named packages in node_modules
   • The fs and path package names on npm are currently benign.

Impact:

• Fixes breaking builds with Next.js
• No security issues introduced by changing the import specifier