test: use fs.execFile instead of exec

[targos]

Generally safer than building a shell script, and allows to run the
tests from a directory with spaces in it.

[targos]

Example failure

​ FAIL ​ test/pkg/pkg.test.js
 ✖Command failed: npx pkg /Users/mzasso/git/forks/pino with spaces/test/pkg/index.js --config /Users/mzasso/git/forks/pino
  with spaces/test/pkg/pkg.config.json (node:8620) [DEP0040] DeprecationWarning: The `punycode` module is deprecated.
  Please use a userland alternative instead. (Use `node --trace-deprecation ...` to show where the warning was created)

  test: worker test when packaged into executable using pkg
  at:
    line: 983
    column: 15
    file: node:internal/errors
    function: genericNodeError
  code: 2
  killed: false
  signal: null
  cmd: npx pkg /Users/mzasso/git/forks/pino with spaces/test/pkg/index.js --config
    /Users/mzasso/git/forks/pino with spaces/test/pkg/pkg.config.json
  stdout: "> pkg@6.1.1

    > \e[31mError!\e[39m Not more than one entry file/directory is expected\n"
  stderr: >
    (node:8620) [DEP0040] DeprecationWarning: The `punycode` module is deprecated.
    Please use a userland alternative instead.

    (Use `node --trace-deprecation ...` to show where the warning was created)
  tapCaught: returnedPromiseRejection

[targos]

/cc @mcollina It would be nice if we could have a release after this to have a green module in citgm.

[mcollina]

lgtm

[targos]

Damn, on Windows I guess it would have to be npx.cmd. I can either make the executable file conditional or pass { shell: true }. What do you prefer?

[mcollina]

either works, or you can just skip this in citgm.

[mcollina]

let's just skip this test if CITGM is set

[targos]

It doesn't only fix citgm. It's quite common on Windows to have folders with spaces

[mcollina]

lgtm