[kbn/optimizer] Force worker exit, extend parent ping timeout

[spalger]

We're still seeing failures on CI caused by workers who are exiting early (probably because the parent process doesn't response to the ping quickly enough)

As well as workers which don't gracefully close for some reason

We don't know exactly why this is happening, but it's clearly related to the pings we implemented yesterday, hoping that forcefully closing the worker internally, and extending the ping timeout for the parent will be sufficient to avoid this level of failure on CI.

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[mistic]

LGTM

[tylersmalley]

We probably still want to log an error.

[spalger]

What error? If we call process.exit() the process is going to exit immediately and we won't be able to set a timer or anything.

[tylersmalley]

LGTM - just one minor comment.

[kibanamachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request
• Commit: 3be2740
• Pipeline Steps (look for red circles / failed steps)
• Interpreting CI Failures

Failed CI Steps

• Execute kibana-intake

---

Test Failures

Kibana Pipeline / kibana-intake-agent / Jest Integration Tests.src/dev/code_coverage/ingest_coverage/integration_tests.Ingesting coverage to the coverage index should result in every posted item having a site url that meets all regex assertions

Link to Jenkins

Standard Out

Failed Tests Reporter:
  - Test has failed 1 times on tracked branches: https://github.com/elastic/kibana/issues/67075

Stack Trace

Error: Failed: 1
    at Env.fail (/var/lib/jenkins/workspace/elastic+kibana+pipeline-pull-request/kibana/node_modules/jest-jasmine2/build/jasmine/Env.js:778:61)
    at ChildProcess.next (/var/lib/jenkins/workspace/elastic+kibana+pipeline-pull-request/kibana/node_modules/jest-jasmine2/build/queueRunner.js:31:24)
    at ChildProcess.emit (events.js:198:13)
    at maybeClose (internal/child_process.js:982:16)
    at Socket.stream.socket.on (internal/child_process.js:389:11)
    at Socket.emit (events.js:198:13)
    at Pipe._handle.close (net.js:607:12)

---

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[spalger]

I'm just going to revert the changes I've made to the optimizer recently, there is clearly something wrong with the strategy here and I'm really unsure that this is going to make things better.