refactor: move product validation logic to dedicated middleware

[jikrana1]

📋 Pull Request — Extract Product Validation into Dedicated Middleware

🔗 Related Issue

Closes #243

---

📝 Summary

Refactored product validation logic by moving request validation out of the routes file into a dedicated middleware module. This improves code organization, readability, and maintainability.

✨ Changes Made

• Created a separate productValidator.js middleware file.
• Moved create product validation logic into validateCreateProduct.
• Moved update product validation logic into validateUpdateProduct.
• Updated product routes to use the new validation middleware.
• Reduced clutter in the routes file and improved separation of concerns.
• Kept validation behavior unchanged while making the codebase more modular.

🎯 Benefits

• Cleaner and more maintainable route definitions.
• Better separation of responsibilities.
• Easier to extend and reuse validation logic in the future.
• Improved overall project structure and readability.

🧪 Tested

• ✅ Create Product API
• ✅ Update Product API
• ✅ Validation error responses
• ✅ Route functionality remains unchanged

[vercel]

Someone is attempting to deploy a commit to the Bhuvansh's projects Team on Vercel.

A member of the Team first needs to authorize it.

[BHUVANSH855]

LGTM