test: Fix flaky babel-cli test

[JLHwung]

Q	A
Fixed Issues?	Second attempt (after #14385) to fix flaky babel-cli test
Patch: Bug Fix?
Major: Breaking Change?
Minor: New Feature?
Tests Added + Pass?	Yes
Documentation PR Link
Any Dependency Changes?
License	MIT

[babel-bot]

Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/51892/

[nicolo-ribaudo]

We could also just retry the test 3 times if it fails.

[JLHwung]

We could also just retry the test 3 times if it fails.

That would have to be implemented in the test executor. I am avoiding that since the --verbose one seems to be the only flaky babel-cli test now.

[liuxingbaoyu]

We should probably use the readline package.

Because inputs are sometimes merged.

:)

FAIL  packages/babel-cli/test/index.js (32.406 s)
bin/babel > dir --out-dir --watch --verbose with external dependencies
    Error: "/home/runner/work/babel/babel/packages/babel-cli/lib/babel" "src" "--out-dir" "lib" "--watch" "--verbose": stderr:
    ["src/index.js -> lib/index.js\nsrc/main.js -> lib/main.js"]
    "Successfully compiled 2 files with Babel (123ms)."

["src/index.js -> lib/index.js\nsrc/main.js -> lib/main.js"]

[JLHwung]

After 6ea0e60 I have run CI test for five times. The good news is that I didn't see one babel-cli test failing, the bad news is that this one surfaces to be our new flaky error:

Parsing error: Cannot destructure property 'message' of 'WorkerClient[#worker_threads].receiveMessageOnPort(...)' as it is undefined.

[nicolo-ribaudo]

Yeah, we have had that error for one week, I spend multiple hours debugging it but didn't come to a conclusion 😬

[liuxingbaoyu]

Looks like it can also be reverted.

[JLHwung]

I am merging with one 👍 because this PR only update test files.