stream: handling invalid stream arguments in `stream.pipeline()`

A few "what goes where"-related inconsistencies with `stream.pipeline()`. Validation of stream objects is very hit-and-miss: <table> <thead> <th>Passing this:</th> <th>as this:</th> <th>should do this:</th> <th>and does this:</th> </thead> <tbody> <tr> <td rowspan="3">Non-readable Node stream</td> <td>source</td> <td>Should be rejected.</td> <td>:x: <a href="https://github.com/nodejs/node/blob/deb5effe017aa10e4fd1e0ce798236e38a432c77/lib/internal/streams/pipeline.js#L306-L308">Passes validation</a>. Gets passed to <code>Duplex.from()</code>, resulting in a write-only Duplex. The pipeline will never receive any data.</td> </tr> <tr> <td>transform</td> <td>Should be rejected.</td> <td>:heavy_check_mark: Fails validation.</td> </tr> <tr> <td>destination</td> <td>Should be accepted.</td> <td>:heavy_check_mark: Passes validation.</td> </tr> <tr> <td rowspan="3">Non-writable Node stream</td> <td>source</td> <td>Should be accepted.</td> <td>:heavy_check_mark: Passes validation.</td> </tr> <tr> <td>transform</td> <td>Should be rejected.</td> <td>:x: <a href="https://github.com/nodejs/node/blob/deb5effe017aa10e4fd1e0ce798236e38a432c77/lib/internal/streams/pipeline.js#L376">Passes validation</a>. Fails asynchronously at runtime: when the previous stream in the pipeline emits data, raises a TypeError due to attempting to call missing Writable methods.</td> </tr> <tr> <td>destination</td> <td>Should be rejected.</td> <td>:x: Same as above.</td> </tr> <tr> <td rowspan="3"><code>ReadableStream</code></td> <td>source</td> <td>Should be accepted.</td> <td>:heavy_check_mark: Passes validation.</td> </tr> <tr> <td>transform</td> <td>Should be rejected.</td> <td>:heavy_check_mark: Fails validation.</td> </tr> <tr> <td>destination</td> <td>Should be rejected.</td> <td>:x: <a href="https://github.com/nodejs/node/blob/deb5effe017aa10e4fd1e0ce798236e38a432c77/lib/internal/streams/pipeline.js#L395">Passes validation</a>. Fails asynchronously at runtime: raises a TypeError due to attempting…