fix(conn): properly inspect interfaces for nil values

[epelc]

Fixes #773 by further inspecting arguments to check if they are nil interfaces or slices.

Sending a nil byte slice use to not work because it was a nil value of type []byte which != nil hence it would really send an empty byte slice. This prevented you from setting columns to null unless you had a different path to send an explicit nil which also had no type(confusing and a pain to implement). Checking interface values equal nil is a common bug in go which usually requires using the reflect package to further inspect the interface's actual value is nil since the typing usually isn't.

This does slightly slow down writes theoretically but it should be worth it for such a common use case and standard feature of sending nil.

[dynajoe]

I have a similar issue. What's the best way to go since this PR has been open over a year?