feat: postgrest 13 add maxaffected in client libraries

[avallete]

What kind of change does this PR introduce?

• Implement the maxAffected postgrest 13 feature at the client level
• Add tests, introduce a more generic way to handle Prefer header, can be refactor at other places in other PR
• Refactor the custom made headers handling approach to the standard Headers API
• Bump minimal node version to the latest LTS v18 (which as support for Headers)

[steve-chavez]

@avallete This works for RPC too, could we add it that? The docs have been updated recently (ref, see RPC at the bottom).

[steve-chavez]

A nice-to-have on typescript would be a validation that the function returns SETOF, otherwise the failure would be at runtime I believe.

[avallete]

Good catch didn't tested the rpc they do have their own kind of typing though because they're a bit specifics.

About the "set of" that's actually something I wanna work on. It will be related to "embedded relationships with functions". I have some draft I need to find the time to work on it.

For now I think runtime error is okay, but we'll surely be able to catch that at type level at some point indeed. Just wondering, what if the function doesn't returns a setof but just plain records ? Or return table ?

[steve-chavez]

For now I think runtime error is okay, but we'll surely be able to catch that at type level at some point indeed. Just wondering, what if the function doesn't returns a setof but just plain records ? Or return table ?

Right now it will just fail silently, but we're working on a fix to raise an error.

[avallete]

Added a specific case for RPC calls as we can't really know the request method at type inference time, nor can we know if it returns a `setof` another table. So it'll be a bit of degraded experience typewise (more chances to have error only at runtime) but should be good enough for now.