fix: Fix filtering by categories and collections

[soniaklimas]

I want to merge this change because it fixes filtering by categories and collections while ensuring backward compatibility with existing attribute filtering.

Pull Request Checklist

• Test the changes locally to ensure they work as expected.
• Document the testing process and results in the pull request description. (Screen recording, screenshot etc)
• Include new tests for any new functionality or significant changes.
• Ensure that tests cover edge cases and potential failure points.
• Document the impact of the changes on the system, including potential risks and benefits.
• Provide a rollback plan in case the changes introduce critical issues.
• Update documentation to reflect any changes in functionality.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nimara-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 30, 2024 9:39am
nimara-ecommerce	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 30, 2024 9:39am

[karolkarolka]

check this section https://graphql.org/learn/queries/#directives and extend SearchProductQuery depending on the query's argument named e.g. $searchBy = "category" | "collection" | undefined to create the query response fields dynamically. With that, you can have a single search query with many outputs depending on the URL search param instead of now 3 and having multiple if conditions in your render function. And check if you can reuse GraphQL Fragments because you've repeated in each new query the products query when it should be reused as a Fragment (stored ready-to-use Products Query).

[karolkarolka]

almost done