Teskit doesn't run Neo4j on the localhost and with the same credentials of boltkit, but it exposes
the host and credentials as env variables.

So all this configuration being loaded to karma on the config files, parsed in `shared-neo4j` with fallback to
the process env (case it's running the usual integration test) and to the default boltkit values.

All the integration tests were changed to use the values from the shareNeo4j object.

Disabled tests:
* IPV6 tests are skipped on the testkit because of the lack of support for this
* TLS tests are disabled since it's already tested on the testkit suite
* Tests which depends on the enterprise edition of Neo4j is running only on this scenario

Fix the way the url is generated during the stress test enabling to use configurations came from the test environment.
Skipping the non-cluster-safe stress test commands to avoid unstable behaviours and flaky tests.

The timeout was being defined using the jasmine global variable and it was causing some flakyness in the tests.

 Avoid session.run usage
 Treat the session.close() exception in the command.
 Check the number of commands run

The result summary was not filled with the protocol version because the transactions were creating
the Result object with a empty connection holder. Since the Result releases the connection from holder
when it completes, the original holder could not be passed to it.

The ReadOnlyConnectionHolder provides a safe way to pass the holder forward without let the consumer initialize,
close or release the connection by simulating this methods without do the action and delegating part of the requests to the original ConnectionHolder.

These changes also made shared-neo4j cluster friendly.

…ilable (#664)

The window.location is not available in the WebWorkers contexts and because of the driver keeps wrongly warning about a misconfiguration.
If the information location protocol is not available, the driver should not warning.

This commit adds ability to create type-safe Record entities by assigning type to Record's value.
The implementation is based on adding type parameters to types, interfaces, and classes. It is implemented however in a backwards-compatible manner, so that opting in to type safety is optional.

Examples:

// before (unsafe)
const record = new Record(['name'], ['Alice'])
record.get('neam') // no errors
record.toObject().neam[0] // run-time (late) error

// after (safe)
const record = new Record<Person>(['name'], ['Alice'])
record.get('neam') // Error: does not exist
record.toObject().neam[0] // design-time (early) error

The goal of this change is improve the stability of the stress test avoiding unexpected timeouts. This change also provide a way to configure the stress-test to run for a defined time period, it's particular interesting for when it's running in test-kit in cluster mode simulating the change on the cluster composition.

…ers (#669) (#670)

The lack of set channel._open to false when the onclose event is triggered was causing the channel be broken without the other parts of the driver notice. In tbis way, a next iteration trying to get the broken connection will succeded in the try and run the query will result in a eternal pending promise.

Mark the channel as closed enable the pool to discard and create a new connection if it needed.