Investigate the impact and remove process.stdin.resume()

[nazarhussain]

Expected behavior

Currently we have a usage of process.stdin.resume() in chain module. Which actually come from the legacy code.

lisk-sdk/framework/src/modules/chain/chain.js

Lines 47 to 48 in 942d320

	// Begin reading from stdin
	process.stdin.resume();

While writing storage tests in jest I found out the test runner hangs up after the successful execution and it jest option --detectOpenHandles leads to above line.

For now I had limited it not block stdin during the tests. We should investigate the impact of it in the production environment and then remove it.

Actual behavior

We should not be holding off the stdin in any case.

Which version(s) does this affect? (Environment, OS, etc...)

3.0.0