fix(postgrest): fix maybeSingle for all request methods by removing Accept header override

[mandarini]

Summary

• Removes the Accept: application/vnd.pgrst.object+json header override from maybeSingle() so PostgREST never sends a 406 for 0-row results
• Drops the method === 'GET' guard so client-side array cardinality enforcement applies to all methods (including .insert().select().maybeSingle())
• Removes the "0 rows" string-matching fallback, which is no longer needed

Related supabase/postgrest-js#361

And thanks to supabase/supabase-py#1424

[pkg-pr-new]

Open in StackBlitz

@supabase/auth-js

npm i https://pkg.pr.new/@supabase/auth-js@2182

@supabase/functions-js

npm i https://pkg.pr.new/@supabase/functions-js@2182

@supabase/postgrest-js

npm i https://pkg.pr.new/@supabase/postgrest-js@2182

@supabase/realtime-js

npm i https://pkg.pr.new/@supabase/realtime-js@2182

@supabase/storage-js

npm i https://pkg.pr.new/@supabase/storage-js@2182

@supabase/supabase-js

npm i https://pkg.pr.new/@supabase/supabase-js@2182

commit: 5358c72