doc: update stream.pipeline() signature

[vsemozhetbyt]

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• documentation is changed or added
• commit message follows commit guidelines

The ...transforms parameter seems optional.

Refs:

node/lib/internal/streams/pipeline.js

Lines 130 to 132 in 0875837

	if (streams.length < 2) {
	throw new ERR_MISSING_ARGS('streams');
	}

Refs: https://github.com/nodejs/node/blob/e559842188f541b884abff2ffad4d2d3e1b841a6/doc/api/stream.md#streams-compatibility-with-async-generators-and-async-iterators
(see the last example)

[ronag]

Isn't ...transform already optional by definition? i.e. ... is a sequence which may be empty.

[jasnell]

Yes, but the [ .. ] bracket syntax is more idiomatic across our docs.

[vsemozhetbyt]

Sorry, I did not even consider ... may mean an empty list (i.e. for me it was rather transform+ than transform*). So maybe there are some more readers like me)

[vsemozhetbyt]

And it seems this pattern is used:
console.assert(value[, ...message])
domain.run(fn[, ...args])
emitter.emit(eventName[, ...args])

[lpinca]

Landed in 2f23918.