CommandResponse.console.log buffering to mStdout may cause the node process to fail if it exceeds the heap size limit

[zFernand0]

The CommandResponse.console.log function...
https://github.com/zowe/imperative/blob/741f24f7246028879317dbd9590b91d7efbdef39/packages/cmd/src/response/CommandResponse.ts#L537-L547

Calls writeAndBufferStdout
https://github.com/zowe/imperative/blob/741f24f7246028879317dbd9590b91d7efbdef39/packages/cmd/src/response/CommandResponse.ts#L914-L919

Instead of buffering the data, we could Stream it! For example:

    private writeAndBufferStdout(data: Buffer | string) {
        Readable.from(data).on("data", (chunk) => {
          process.stdout.write(chunk);
        });
    }

The problem with this solution is that streaming is an async operation. In order to guarantee that the data is not piped or printed out of order, the streaming operation has to be promisify-ed.

This means that in order for you to produce output to the terminal, you need to await response.console.log(data), which forces the function that calls this to also be async (and also needs to be await-ed).

[robertblum-psi]

BTW: Same issue affects stderr, and yes huge amounts of data can be sent to stderr.