Repo: handle exceptions that occur while testing a rule better about typescript-eslint

[bradzacher]

The root causes is jest using worker threads and communicating things across threads.

Specifically when you throw an error in a selector eslint will include the current AST node in the error. The AST is cyclic and thus the error.

[JoshuaKGoldberg]

Ha, yeah, I saw this recently and got around it hackily by adding to the file mentioned in the error:

      at messageParent (../../node_modules/jest-worker/build/workers/messageParent.js:29:19)

} else if (typeof parentProcess.send === 'function') {
+   console.log(message?.[1]?.[1]);
    parentProcess.send([_types.PARENT_MESSAGE_CUSTOM, message]); 

Is this a bug in Jest? If so, is it resolved by bumping to the latest version? Someone should look into this. 😄