Import connect into query, connect docstring improvements

[danielcompton]

It is often a pain to have to import the rethinkdb.core namespace just to make a connection. This PR imports the connect function into the rethinkdb.query ns which is the most common ns for API consumers to be using.

I wasn't keen on using something like Potemkin for a single function, sing out if you've got alternative approaches or have an issue with this, otherwise I'll merge this in a few days.

• Add documentation
• Update tests to use new connect function?

[danielcompton]

I have no earthly idea why 441790f fixes the tests, would love for someone else to have a look and tell me why.

[danielcompton]

There may be some conflicts between the close created by the defrecord, and the close function that we define, although I think there's something deeper there too.

[yurrriq]

@danielcompton, on line 27 there's

(def close ...) ; <= for connections

but then on line 34 there's

(defn close ...) ; <= for cursors

So when you

(:require [rehtinkdb.query :as r])

;; ...

(r/close ...)

it refers to the cursor-closing function.

That's my guess anyway.

[yurrriq]

Confirmed:

(in-ns 'rethinkdb.query)
(doc close)

-------------------------
rethinkdb.query/close
([cursor])
  nil
nil

[yurrriq]

Since query/close (the cursor-closing function) simple calls net/close which is just sugar for java.io.Closeable's close, maybe the one in query is overkill..

[danielcompton]

After fixing #50, there's no need to add a query/close function here. I've removed the commits and rebased against master.