fix: Ensure thrown errors have a stack trace (supabase#502)

* Ensure thrown errors have a stack trace

* chore: stricter typing

* chore: update snapshot

---------

Co-authored-by: Bobbie Soedirgo <[email protected]>

fix: add link on how to enable explain on the explain() method (supab…

…ase#507)

* add link on how to enable explain on the explain() method

* Update src/PostgrestTransformBuilder.ts

Co-authored-by: Tyler <[email protected]>

* keep docs link

---------

Co-authored-by: Bobbie Soedirgo <[email protected]>

feat: detect one-to-one relationships

fix: `explain()` always returning an error

It sends `for="application/json"` as media type by default, instead of `for="undefined"`.

fix: detection of maybeSingle

On PostgREST 11.2.0, the format of the error got changed on PostgREST/postgrest#2876 to "The result contains 0 rows".

Change the detection to "0 rows". This should be backwards compatible.

fix: use @supabase/node-fetch

fix: trigger release

fix: revert using @supabase/node-fetch

fix: use @supabase/node-fetch

feat: add dynamic schema to postgrest client

Resolves supabase#280