Deprecate passing ranges to `#in` and `#not_in`

Given that we are going to remove casting from Arel in the near future,
having a single place nodes in predications will help.

This reverts commit 36836fa, reversing
changes made to 53bc842.

This reverts commit 9b92af7.

beta2 is out, and we've fixed the issue that this caused in Rails

It's not quite duck typed, but it will allow us to pass in our own
objects with additional logic (like type casting).

We know the API for the depth first visitor in advance, so it's OK to
calcuate this cache in advance

This removes the need for us to do the re-ordering by walking the AST in
ActiveRecord. We're using a block to communicate with the collector,
since the collector needs to be the thing which knows about the index,
while the visitor is the thing that needs to know the syntax. The
BindParam needs to know about neither of these things, so it's been
changed to stop being a subclass of SqlLiteral

I could also see an alternative implementation using format strings if
for some reason blocks cause a problem.

The only reason we're using strings is to pre-populate the cache, but
`Class#name` returns a new string instance on every call. This is a
pretty major source of memory usage. We don't technically need to
pre-populate the cache, and not doing so allows us to go back to using
cache objects

Support Oracle bind parameter value

remove extra space from select statement

The only place this method was still used is on the MSSQL visitor. The
visitor has all of the objects required to inline this lookup there.
Since the `primary_key` method on the connection adapter will perform a
query when called, we can cache the result on the visitor.

It is never used outside of convenience methods which are only used in
tests. In practice, it just made constructing tables more complicated on
the rails side. This is the minimum possible change to remove the
constructor argument, but continue to have the tests passing.

I'm not sure if we have a reason to keep `project` and friends, and the
solution might actually just be to remove the engine from
`SelectManager` and friends. As such I've held off on deleting those
methods.

We need to figure out what to do with `Table#from`. It's old invocation,
which read `table.from(table)` was certainly nonsensical.

This constructor parameter was unused for everything except the
convenience methods `to_sql` and `where_sql`. We can pass the engine
into those methods directly.

We're going to start working on removing type casting from arel. To
avoid doing one gigantic commit which moves everything over to eager
casting, we need a way to tell Arel that we've already cast it. The
easiest path to that is to give it a quoted node, and then we remove
this case once we're never returning a Casted node

We need to be able to not care which we've gotten in ActiveRecord

`nil?` not `nil`

to_SQL already has supported the ESCAPE clause in rails#318.
PostgreSQL can use the ESCAPE clause too.

Remove Unused `require`

Lateral expressions for PostgreSQL

https://www.ruby-lang.org/en/news/2017/12/25/ruby-2-5-0-released/

Refer ruby/rubygems#2123

Address rails#517

Refer ruby/bigdecimal#86

CI with Ruby 2.5.0