feat(realtime): add predefined filters instead of regular String

[LucasAbijmil]

What kind of change does this PR introduce?

This PR introduces predefined filters for RealtimeChannelV2 instead of using a regular String (see my Feature Request and issue)

What is the current behavior?

A String passed as a parameter by the client (error prone)

What is the new behavior?

Use predefined filters – similar in syntax to a regular query.

[grdsdev]

Thanks for the work here, just a few change requests.

We'd also need some tests for the new filter type.

[LucasAbijmil]

@grdsdev Let me know what you think of my update, and I'll finalize the tests based on your feedback

[coveralls]

Pull Request Test Coverage Report for Build 13441029480

Details

• 25 of 43 (58.14%) changed or added relevant lines in 3 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.1%) to 74.842%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
Sources/Realtime/RealtimePostgresFilterValue.swift	7	10	70.0%
Sources/Realtime/RealtimeChannel+AsyncAwait.swift	0	15	0.0%

Totals
Change from base Build 13424523309:	-0.1%
Covered Lines:	5081
Relevant Lines:	6789

---

💛 - Coveralls

[grdsdev]

You're on the right track, just a few more changes.

[LucasAbijmil]

You're on the right track, just a few more changes.

I hope you'll enjoy the changes :)

[AronnK]

Hey! So I'm trying to have 2 filters in my code, one .eq to a row and one change in a specific column (corresponding to that row)
So is it possible to do it now by using AND or some other means?

[grdsdev]

Hi @AronnK multiple filters aren't supported yet, follow the thread supabase/realtime-js#97 to know more.

[AronnK]

Hi @AronnK multiple filters aren't supported yet, follow the thread supabase/realtime-js#97 to know more.

Hey @grdsdev, thanks for the information!