0.1.0 - Timeouts rework, command method

[slvrtrn]

Summary

• Resolves 3 seconds delay when max_open_connections is set #161
• node-abort-controller dependency is removed
• insert response stream is destroyed immediately
• command method is introduced
• We are now relying on signals that are passed to the request instead of setting sockets timeouts

Changelog:

Breaking changes

• connect_timeout client setting is removed, as it was unused in the code.

New features

• command method is introduced as an alternative to exec.
  command does not expect user to consume the response stream, and it is destroyed immediately.
  Essentially, this is a shortcut to exec that destroys the stream under the hood.
  Consider using command instead of exec for DDLs and other custom commands which do not provide any valuable output.

Example:

// incorrect: stream is not consumed and not destroyed, request will be timed out eventually
await client.exec('CREATE TABLE foo (id String) ENGINE Memory')

// correct: stream does not contain any information and just destroyed
const { stream } = await client.exec('CREATE TABLE foo (id String) ENGINE Memory')
stream.destroy()

// correct: same as exec + stream.destroy()
await client.command('CREATE TABLE foo (id String) ENGINE Memory')

Bug fixes

• Fixed delays on subsequent requests after calling insert that happened due to unclosed stream instance when using low number of max_open_connections. See #161 for more details.

Checklist

• Unit and integration tests covering the common scenarios were added
• A human-readable description of the changes was provided to include in CHANGELOG
• For significant changes, documentation in /~https://github.com/ClickHouse/clickhouse-docs was updated with further explanations or tutorials - see ClickHouse-JS 0.1.0 update clickhouse-docs#1252