fix(supabase): handle multiple filters in realtime subscriptions

[s3ldc]

PR Checklist

• 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?

When using the Supabase live provider with multiple filters, refine joins the filters with commas and sends them in a single realtime subscription.
Supabase Realtime does not support multiple filters in this format, causing invalid payloads and broken realtime subscriptions.

What is the new behavior?

If multiple filters are provided, the provider now logs a warning and applies only the first filter.
This prevents invalid realtime payloads and allows subscriptions to continue working.

Fixes #6360

Notes for reviewers

Supabase Realtime currently supports only one filter per subscription.
This change adds a defensive guard to avoid silent failures when multiple filters are passed.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3b79e65

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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