Fix: Implement product sorting and improve dropdown functionality

[AparAgarwal]

This pull request refactors product sorting to be handled server-side instead of client-side, updates the product sorting API and UI, and improves several UI components for better user experience and accessibility. The most significant changes include moving sorting logic to the backend, updating the API and Redux actions to support this, improving the sort dropdown menu, and enhancing the product rating display.

Backend Sorting & API Integration:

• Refactored the getProducts API function to support a sort parameter, which triggers a backend endpoint for sorted results. The function now also normalizes the API response for both array and object data.
• Updated the Redux fetch action in Products.jsx to always include a backend sort key, defaulting to 'feature', and mapped UI sort selections to backend-supported sort keys.

Client-Side Code Simplification:

• Removed all client-side sorting logic from the Products page; now, the displayed products are directly sliced from the filtered list, relying on the backend to provide the sorted data.

Sort Dropdown UI/UX Improvements:

• Improved the sort dropdown to remain open during page scroll (per UX requirements), only closing when clicking outside or the close button. Added a close ("X") button and smooth open/close transitions. The dropdown is now more accessible and visually refined.

Product Card UI Enhancement:

• Updated the product rating display to support fractional (partial) stars, showing more accurate ratings visually with partially filled stars.

Minor UI Consistency:

• Added cursor-pointer to clickable elements for better visual feedback.

These changes together ensure that product sorting is more efficient, accurate, and user-friendly, leveraging backend capabilities and improving the frontend experience.

[AparAgarwal]

Updates made as outlined in:

• Implement Sort Functionality on All Products Page .github#96
• fix: update sorting options to use 'Featured' instead of 'Best Selling' #104
• refactor: update component styles and structure for improved consistency and responsiveness #107

[AparAgarwal]

@Alexandrbig1 I’ve removed the client-side filtering logic for the sake of code simplification. However, if needed, I can reintroduce it as a fallback in case of backend response errors. Please review the changes and let me know your thoughts.
Thanks!

[Alexandrbig1]

Thank you for your contribution, and congrats on your PR being approved!
We’re excited to have your work as part of Open Code Chicago’s Hacktoberfest 2025 project.

[Alexandrbig1]

I’ve removed the client-side filtering logic for the sake of code simplification. However, if needed, I can reintroduce it as a fallback in case of backend response errors. Please review the changes and let me know your thoughts.
Thanks!

@AparAgarwal, removing client-side filtering is fine for simplicity, but note that a backend error could leave no products. Reintroduce a client-side fallback if reliability matters. Otherwise, keep it removed. Please decide.

[AparAgarwal]

@AparAgarwal, removing client-side filtering is fine for simplicity, but note that a backend error could leave no products. Reintroduce a client-side fallback if reliability matters. Otherwise, keep it removed. Please decide.

Thanks for the clarification.

Given the current priorities, I’ll keep the client-side filtering removed to keep the codebase simpler. If we encounter backend reliability issues or missing product data in the future, The client-side fallback can be reintroduced as needed.

[Alexandrbig1]

@AparAgarwal, sounds good! If backend issues arise, reintroducing a client-side fallback is a good plan. Thanks.