feat(postgrest)!: stronger type system for query building

[Vinzent03]

What kind of change does this PR introduce?

feature

What is the current behavior?

The type system makes everything dynamic, which is not very efficient. Additionally, the way a method argument changes the overall return type is not very darty.

What is the new behavior?

By changing the api and class structure, everything is perfectly typed.

Before

supabase.from('users').insert().select<PostgrestListResponse>('id, messages', FetchOptions(count: CountOption.exact));

supabase.from('users').select('id, messages', FetchOptions(count: CountOption.exact));

supabase.from('users').select('*', FetchOptions(count: CountOption.exact, head: true));

After

supabase.from('users').insert().select('id, messages').count(CountOption.exact);

supabase.from('users').select('id, messages').count(CountOption.exact);

supabase.from('users').count(CountOption.exact);

Breaking points

• FetchOptions is removed from select etc. and made to stand alone methods

Additional context

The pr turned bigger than expected, but I think it's real magic how the return type perfectly changes by adding single and withConverter etc. So I think it's worth it.

[Vinzent03]

This should be ready now 🚀
I'm just unsure about one thing. Is there a real use case for the following query?

await postgrest.from('users').select('*').head();

I've made it void now, because it calls the query, but doesn't return it? I'm unsure what to put in the documentation as well.

[dshukertjr]

This looks amazing! I had a few small questions here and there, but nothing major! Thanks for the awesome work 🚀

[Vinzent03]

Other than the head thing, everything should be fixed