rspec integration in rake file

These run all the integration tests from sequel against fdbsql
Fail if integration uri isn't fdbsql://

Because that's not useful, you could just run the integration specs
in sequel
Added initial docs for running tests
Require the lib folder; don't use the gem

so that you test the current code, not the last packaged code
"Pass" drop_table :if_exists (but still not real)

drop_table? just prints drop_table was called, meaning there should
be substantially less errors
Added vacuous connection object
Actually use a pg connection that's for real

I checked, and it complained that the server wasn't running,
and failed test, then passed the tests when I started the sql-layer
DROP TABLE IF EXISTS works
Restrict to not use 2.99.0

it seems like that's basically 3.0.0, so I'm a bit cautious of using it
Almost parse schema table, rows need to be symbols
Updated comment to be more relevant
Successfully create tables

This passes the test:
Database schema modifiers should create tables correctly
and a bunch of others, so now 57 tests are passing
was 5
Added WARN: DROP_TABLE IF EXISTS note

People might get worried about all the WARN lines printed out in
the test output
Removed regex filtering out sql statements
Use serial type instead of autoincrement

good for creating primary keys
Added support for Insert Returning

598 -> 600 examples run
535 -> 504 failures
Added Connection.execute

This causes the following test to pass
  Sequel::Model Simple Associations should handle eager loading
      limited associations for many objects
600 -> 600 examples
504 -> 487 failing
Return res.tuples (count of updates)

This brought one test forward, and fixed a buncgh of others
the yield value is still the PG::Result

600 -> 600 examples
487 -> 458 failures
Convert result values to ruby types

This uses the PG_TYPES list of converter methods to make various
result values there actual ruby types (e.g. int)

600 -> 600 examples
458 -> 273 failures
Fixed naming conflict with instance variable

I don't know where, or what was setting @columns, but it was being
set to more than the actual column names.
This might have introduced a new problem, because some of the tests
might be failing for not having all the column names they need...

600 -> 600 examples
273 -> 254 failures