Errors thrown by failed requests should contain information about the query or source location that caused them #75
Description
Suppose you have a service and somewhere inside of it, too few parameters are passed to a query. This will result in an error Error: Invalid query: Invalid amount of bind variables to be thrown but without an attached debugger or additional logging, it’s almost impossible to tell, which query caused this issue.
postgres-nio, for example, captures the #fileID and #line of the caller in the query method and enriches any errors with that source information, in addition to the executed query. It would be great if swift-cassandra-client could consider doing the same or something similar to throw more actionable errors.