fix(supabase): parse nested values correctly when using conditional filters

[pkarc]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://refine.dev/docs/guides-concepts/contributing/#commit-convention

Bugs / Features

• Related issue(s) linked
• Tests for the changes have been added
• Docs have been added / updated
• Changesets have been added https://refine.dev/docs/guides-concepts/contributing/#creating-a-changeset

What is the current behavior?

Consider the following filter:

const filter: CrudFilter = {
  operator: 'or',
  value: [
    {
      field: 'name',
      operator: 'contains',
      value: 'foo',
    }
  ],
};

resolve to (name.ilike.foo) giving no results

What is the new behavior?

The filter should resolve to (name.ilike.%foo%)

fixes (#6239)

Notes for reviewers

If you consider having extra tests, I can add some to cover it fully

[changeset-bot]

🦋 Changeset detected

Latest commit: 05da092

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@refinedev/supabase	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[aliemir]

Hey @pkarc thank you for the PR! There was a small lint issue, I've sent a small fix for it. We'll include this change in our next release 🙏