Replace readline with message transport

[TiagoSeverino]

This change is 

[pierreminiggio]

• We're throwing an exception without closing the browser, which will lead to unexpected behaviours (node process still running, maybe chromium processes stackings, etc.). So close that browser before throwing.

• I think we should handle no code being inputed, either through a try catch, or by allowing the signature to return null (so then we can check if "code" is empty or not).
  We probably want to close the browser and end end the execution of the function if the user doesn't input a code or inputs an empty one.

Example of browser closing + throw if you need one :

youtube-uploader/src/upload.ts

Lines 171 to 174 in bba5de3

	if (errorMessage) {
	await browser.close()
	throw new Error('Youtube returned an error : ' + errorMessage)
	}

[TiagoSeverino]

Gonna add the input and exception handling.

[pierreminiggio]

@dement6d This MR impacts the changes you've made here : #101.
This means that if this MR gets merged and you update, you'll have to specify your readline callback through the messageTransport parameter.

[pierreminiggio]

@fawazahmed0 Everything in this MR looks all right to me, I just think the update implementing this MR should be considered a major one when it comes to the version of the package (so 2.0.0), because it will force people who relied on the readline implemented here #101 to implement their own readline callback.

[TiagoSeverino]

@fawazahmed0 Everything in this MR looks all right to me, I just think the update implementing this MR should be considered a major one when it comes to the version of the package (so 2.0.0), because it will force people who relied on the readline implemented here #101 to implement their own readline callback.

Maybe we can default onSmsVerificationCodeSent to the old implementation using readline

[pierreminiggio]

Maybe we can default onSmsVerificationCodeSent to the old implementation using readline

I'm not sure we want that because #153.
By keeping readline, we're basically forcing people not being able to use the LTS version of NodeJS.

[fawazahmed0]

Thanks @pierreminiggio and @TiagoSeverino , I will merge this PR. In future I may still add code from Nodejs current version if necessary.