feat: fix filters attribute name

[Marc-Roig]

What does it do?

As seen in #21338 , attribute names called filters broke the populate validation.
That's cause it was confusing a "filter" inside a populate with the filters attribute name:

{
  populate: {
    foo: {
      filters: { bar: { $eq: 1 } }  // Should filter entries where bar is 1
    }
  }
}

{
  populate: {
    foo: {
      populate: {
        filters: true  //  Should populate the "filters" attribute
      }
    }
  }
}

The traverseQueryPopulate was assuming filters was an attribute, as it was an actual attribute of the schema. Hence the first query was always invalid.

This PR solves this by modifying the traverseQueryPopulate and tracking each traversed node parent.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
contributor-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 25, 2024 8:38am

[Marc-Roig]

@alexandrebodin @innerdvations @Convly I think this might be easier if we spend 15 minutes on discord discussing this ticket together 🤞

[Convly]

Agree, lots of things to say 😂

[Marc-Roig]

@Convly @alexandrebodin if we agree this is what we want to merge, could we have a last look and proceed with it? 🙏

[Convly]

Seems like unit tests are failing, the rest lgtm