Better error messages

[darora]

Both server & client side logs are provided where applicable.

• if query is not provided

Before (think the server also crashes?):

TypeError: Client was passed a null or undefined query
    at Client.query (/Users/darora/src/supabase/postgres-meta/node_modules/pg/lib/client.js:505:13)
   [...]
[ERROR] 08:01:52 TypeError: Client was passed a null or undefined query

* Empty reply from server
* Closing connection 0
curl: (52) Empty reply from server

After:

{"level":"error","time":"2022-01-18T00:06:44.730Z","pid":77960,"hostname":"Divs-MacBook-Pro.local","error":"Error: query not found","request":{"method":"POST","url":"/query","pg":"localhost"}}

< HTTP/1.1 500 Internal Server Error
< 
* Connection #0 to host localhost left intact{"error":"query not found"}%      

(ideally this would be a 400, but I don't want to undertake a bigger refactoring right now)

• if connstring can't be processed

Before:

{"statusCode":500,"error":"Internal Server Error","message":"Cannot read property 'charAt' of undefined"}% 

After:

{"level":"warn","time":"2022-01-18T00:11:20.915Z","pid":85773,"hostname":"Divs-MacBook-Pro.local","reqId":"req-1","message":"failed to parse encrypted connstring","error":"Error: Malformed UTF-8 data"}
{"level":"error","time":"2022-01-18T00:11:20.915Z","pid":85773,"hostname":"Divs-MacBook-Pro.local","error":"Error: failed to process upstream connection details","request":{"method":"POST","url":"/query","pg":"unknown"}}

* Mark bundle as not supporting multiuse
< HTTP/1.1 500 Internal Server Error
* Connection #0 to host localhost left intact
{"error":"failed to process upstream connection details"}%

[github-actions]

🎉 This PR is included in version 0.31.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀