option to run jq as detached process

[sovcharenko]

when an app receives SIGTERM it propagates it to a child jq process and node-jq throws an error.

this makes graceful shutdown of an app impossible.

this PR allows jq to run as detached process so that SIGTERM is not propagated allowing it to exit normally.

[davesnx]

Hey, Thanks for the PR. Can you include a section into the REAMDE in form of docs? I belieb this can be useful to others as well

[sovcharenko]

Done @davesnx , have a look. I also added simple docs for cwd as they were missing

[sovcharenko]

qq - any chance new version will be released soon?

[davesnx]

Commits were not annotated properly, will run a release now.

[sovcharenko]

hm something's wrong. version 4.0.1 doesn't incorporate my changes

[davesnx]

Something seems broken in our release process, released a 4.0.2: https://github.com/sanack/node-jq/releases/tag/v4.0.2

[sovcharenko]

looks like there is a new problem

this is how installed node-js looks:

lib has 'old' code, while src is the latest

and package.json main refers to the stale code.

[sovcharenko]

feels like npm run build and npm run copy-ts-defintions didn't run during release