Update SQLite3 to 3.30.1

sha1sum
```
8383f29d53fa1d4383e4c8eb3e087f2ed940a9e0  sqlite-autoconf-3300100.tar.gz
```

sha256sum
```
8c5a50db089bd2a1b08dbc5b00d2027602ca7ff238ba7658fabca454d4298e60  sqlite-autoconf-3300100.tar.gz
```

Verified to match https://sqlite.org/download.html

* prebuilt: add electron 6.0.0

* node: use Node 6 for test suite

Raspbian is used as base

It took less than 20 min to build on Ubuntu 18.04 x86_64

If merged other arch will come next, and then automated by CI.

Relate-to: https://github.com/mapbox/node-sqlite3/issues/418
Change-Id: Ic92baf3e019e28862a24d84728835a641a6838c1
Forwarded: https://github.com/mapbox/node-sqlite3/pull/1169
Signed-off-by: Philippe Coval <p.coval@samsung.com>

* add electron 4.1 and 4.2

* add electron 4.1 and 4.2 for windows

Use https: instead of http:

ci: use trusty to compile for node12

It took less than 10 min to build on Ubuntu 18.04 x86_64

If merged other arch will come next, and then automated by CI.

Bug: https://github.com/mapbox/node-sqlite3/issues/903
Forwarded: https://github.com/mapbox/node-sqlite3/pull/1147
Change-Id: Ic91292879deed92fcffd90d7b2d79f551c5b06f4
Signed-off-by: Philippe Coval <p.coval@samsung.com>

tests: wait for the backup to complete before finishing it
tests: only trigger internal backup (from main to temp tables) when version is larger or equal to 3.26

This exposes the sqlite3 backup api as described at https://sqlite.org/backup.html.

This implementation draws on https://github.com/mapbox/node-sqlite3/pull/883,
extending it to create a backup object that can be used in the background,
without leaving the database locked for an extended period of time.  This is
crucial for making backups of large live databases in a non-disruptive manner.
Example usage:

```
var db = new sqlite3.Database('live.db');
var backup = db.backup('backup.db');
...
// in event loop, move backup forward when we have time.
if (backup.idle) { backup.step(NPAGES); }
if (backup.completed) { /* success! backup made */  }
if (backup.failed)    { /* sadness! backup broke */ }
// do other work in event loop - fine to modify live.db
...
```

Here is how sqlite's backup api is exposed:

 * `sqlite3_backup_init`: This is implemented as `db.backup(filename, [callback])`
   or `db.backup(filename, destDbName, sourceDbName, filenameIsDest, [callback])`.
 * `sqlite3_backup_step`: This is implemented as `backup.step(pages, [callback])`.
 * `sqlite3_backup_finish`: This is implemented as `backup.finish([callback])`.
 * `sqlite3_backup_remaining`: This is implemented as a `backup.remaining` getter.
 * `sqlite3_backup_pagecount`: This is implemented as a `backup.pageCount` getter.

Some conveniences are added in the node api.

There are the following read-only properties:
 * `backup.completed` is set to `true` when the backup succeeeds.
 * `backup.failed` is set to `true` when the backup has a fatal error.
 * `backup.idle` is set to `true` when no operation is currently in progress or
   queued for the backup.
 * `backup.remaining` is an integer with the remaining number of pages after the
   last call to `backup.step` (-1 if `step` not yet called).
 * `backup.pageCount` is an integer with the total number of pages measured during
   the last call to `backup.step` (-1 if `step` not yet called).

There is the following writable property:
 * `backup.retryErrors`: an array of sqlite3 error codes that are treated as
   non-fatal - meaning, if they occur, backup.failed is not set, and the backup
   may continue.  By default, this is `[sqlite3.BUSY, sqlite3.LOCKED]`.

The `db.backup(filename, [callback])` shorthand is sufficient for making a
backup of a database opened by node-sqlite3.  If using attached or temporary
databases, or moving data in the opposite direction, the more complete
(but daunting) `db.backup(filename, destDbName, sourceDbName, filenameIsDest, [callback])`
signature is provided.

A backup will finish automatically when it succeeds or a fatal error
occurs, meaning it is not necessary to call `db.finish()`.
By default, SQLITE_LOCKED and SQLITE_BUSY errors are not treated as
failures, and the backup will continue if they occur.  The set of errors
that are tolerated can be controlled by setting `backup.retryErrors`.
To disable automatic finishing and stick strictly to sqlite's raw api,
set `backup.retryErrors` to `[]`.  In that case, it is necessary to call
`backup.finish()`.

In the same way as node-sqlite3 databases and statements, backup methods
can be called safely without callbacks, due to an internal call queue.  So
for example this naive code will correctly back up a db, if there are
no errors:
```
var backup = db.backup('backup.db');
backup.step(-1);
backup.finish();
```

Usage:
```
docker build .
```
This can be then declined for several arch, elsewhere.

Change-Id: I79000463955d16eec8809c870f7d02c60da53432
Bug: https://github.com/mapbox/node-sqlite3/issues/418
Forwarded: https://github.com/mapbox/node-sqlite3/pull/1112
https://github.com/mapbox/node-sqlite3/pull/1028
Origin: https://github.com/tizenteam/node-sqlite3
Signed-off-by: Philippe Coval <p.coval@samsung.com>

* Update brew (build_against_electron.sh)

* Update brew (build_against_node.sh)

* make compatible with V8 7.1

* Remove use of two argument Concat

* fixup! bump nan

* 4.0.5
* SQLite 3.26
* electron 4 

fix #1032: add constants for file open

Fix compile issue introduced by nodejs change (increment node-pre-gyp version)

Allow specifying the python to use.