(#136) - Fix "changes since old style" test against CouchDB 2.0

CouchDB 2.0 does not use numeric sequence numbers so we cannot predict the
value that will be returned. Change the test to use the sequence number
returned by the database rather than assuming it will be a specific number.
(#3254) - Disable test temporarily
(#3195) - Stringify "since" parameter when calling _changes

CouchDB 2.0 represents sequence numbers as an array. Ensure we stringify
the array before passing it as a query parameter.

This commit also reverts 8961f5e - stringify should occur when building the
HTTP request instead (which should catch this globally).
(#136) - Fix "changes since new style" against CouchDB 2.0

CouchDB 2.0 does not use numeric sequence numbers so we cannot predict the
value that will be returned. Change the test to use the sequence number
returned by the database rather than assuming it will be a specific number.
(#136) - Fix "Changes limit and filter" against CouchDB 2.0

Do not assume incremental sequence numbers in the test.
(#3259) - Updated links to point to new repo location
(#3252) - Use array.reduce instead of array.forEach

Makes this method a little neater by using reduce instead of forEach.
(#136) - Fix "changes since and limit old style" against CouchDB 2.0

Similar to previous fixes, we cannot assume incremental sequence numbers
in CouchDB 2.0, so ask the server for a valid sequence number and use that
as the since parameter.
(#136) - Fix "Changes Since and limit Old Style limit 0" against CouchDB 2.0

Do not assume incremental sequence numbers in the tests.
(#136) - Fix "Changes Since and limit New Style limit 0" against CouchDB 2.0

Do not assume incremental sequence numbers in the test.
(#136) - Fix "Changes limit New Style" against CouchDB 2.0

Do not assume incremental sequence number in the test.
Use consistent spacing in 'Create/update' heading
(#3229) - Fix global access for node-webkit
(#136) - Fix "Changes since and limit new style" against CouchDB 2.0

Similar to previous commits, do not assume incremental sequence numbers.
(#136) - Fix "Changes limit old style" against CouchDB 2.0

Do not assume incremental sequence numbers in the test.
(#1738) - single batch() for leveldb bulkDocs()

This modifies leveldb's `bulkDocs()` so that it does
everything in a single batch. Note the addition
of the LevelTransaction to make it easier to
accomplish this.

`leveldb.js` is also refactored to use utils.processDocs,
just the same as idb and websql, cutting down on
code duplication.
(#136) - Ignore "changes last seq" against CouchDB 2.0

In clusterd CouchDB, the sequence number returned to the client is an
encoded representation of the various shard states. Whilst the last
"seq" value in _changes.results and the "last_seq" field should evaluate
to the same thing on the server, their encoded representation may differ.
Therefore, the assertions in this test don't hold for clustered CouchDB.
(#136) - Ignore tests for #3136 against CouchDB 2.0

These appear to be testing the internal PouchDB implementation of _changes.
Many of the assumptions don't hold against clustered CouchDB so skipping
them for now.
(#136) - Fix "changes limit and view instead of filter" against CouchDB 2.0

Do not assume incremental sequence numbers in the test.
This commit also adds a helper function to dig out specific items from
_changes (seems the simplest possible solution rather than importing
lodash or similar).
Merge pull request #3249 from willholley/136-changes-limit-and-view-instead-of-filter

(#136) - Fix "changes limit and view instead of filter" against CouchDB 2.0