refactor!(supabase): disallow multiple stream filter

[Vinzent03]

What kind of change does this PR introduce?

Improves developer experience around filtering .stream()

What is the current behavior?

Users could chain multiple filters on .stream() and it would not throw static error. Users could only find out that it's invalid after running the code.

supabase.from('table')
  .stream([])
  .eq('column', 'val')
  .neq('another_column', 'val')
  .lt('third_column', 'val')
  .listen((_) {});

What is the new behavior?

The above example fails at the .new statically. Additionally, I exported the SupabaseStreamBuilder class

Additional context

There was already a pr, but I think the effort of creating classes for order and limit are worth it, because I see no sense in wanting to call the same method multiple times, so I don't disallow it.

[dshukertjr]

Thanks for this. Just had one thing about assertion, but otherwise looks amazing!