[bug]: TypeError [ERR_INVALID_ARG_TYPE] in node application

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current behavior

* While running my node 20 application I face the error of
```
TypeError [ERR_INVALID_ARG_TYPE]: The "code" argument must be of type number. Received type string ('128SIGINT')
at process.set [as exitCode] (node:internal/bootstrap/node:123:9)
at ChildProcess. (/usr/lib/node_modules/nyc/node_modules/foreground-child/index.js:63:22)
at ChildProcess.emit (node:events:519:28)
at maybeClose (node:internal/child_process:1105:16)
at ChildProcess._handle.onexit (node:internal/child_process:305:5) {
code: 'ERR_INVALID_ARG_TYPE'
}
```

### Steps to reproduce

* This is a ```foreground-child``` lib issue which is a part of NYC.
* https://github.com/npm/cli/issues/6766 is the issue in npm cli/
* Use `--skip-coverage=true` to avoid this issue.

### Environment

None

### Version

Cloud

### Repository

keploy

Start by reproducing the Node 20 failure in the coverage path and compare it with the linked npm CLI issue. Inspect the foreground-child stack shown in the report and verify that the chosen change prevents the ERR_INVALID_ARG_TYPE failure without requiring --skip-coverage=true.

Written by the indexing model from the issue text.