Stop silencing errors during launchNode startup

[arboleya]

When using the launchNode utility, some node startup errors derived from improper configs are silenced.

This makes debugging issues tricky and prevents the utility from working as expected.

Reported by @LuizAsFight

[nedsalk]

@LuizAsFight it would be great if you could give an example here for us to have something concrete to work with.

[petertonysmith94]

Could this be related to #2483 do you think @nedsalk?

[nedsalk]

@petertonysmith94 it might be because the child's stdout and stderr are piped into the corresponding process methods.

[arboleya]

Could it be resolved together?

[LuizAsFight]

I don't have one example now @nedsalk , but I remember I got this by informing incorrect chainConfig or incorrect initialization params, then the error produced by the node when starting it was not being shown

[nedsalk]

@arboleya yeah, I'll do it in #2483. I'll put that PR into draft mode until I cover everything there.