doc: standardize rest parameters

[TimothyGu]

Checklist

• documentation is changed or added
• commit message follows commit guidelines

Affected core subsystem(s)

doc

Description of change

Current, rest parameters in API documentation take a variety of inconsistent forms, many of which cause the JSON documentation generator to emit a warning such as the following:

Warning: invalid param "..."
> {"textRaw":"`string` {string} The message to print to `stderr` ","name":"string","type":"string","desc":"The message to print to `stderr`"}
> util.error([...])

This pull request adopts a consistent form of documenting rest parameters, that fits the ES2015 syntax and is digestible for the documentation generator.

One caveat is that this PR changes the anchors of numerous functions, which may break links on the Internet. I could manually add <a id> to mitigate that, so let me know if that is preferred.

[addaleax]

Thanks, LGTM!

I could manually add <a id> to mitigate that, so let me know if that is preferred.

Hmm. We have been pretty liberal with changing these so far, and definitely thank you for taking care of the internal links that would otherwise have been broken…

[cjihrig]

LGTM. As long as the internal links in the docs are working, I think we're fine. As @addaleax said, we've changed these pretty freely in the past. We haven't started considering documentation link changes as semver major... YET.

[lpinca]

Capitalize the type so it will be properly linked.

[TimothyGu]

Fixed.

[lpinca]

LGTM

[jasnell]

LGTM

[lpinca]

Landed in e1ddcb7, thanks!