doc: prevent one more false-positive linkification

[vsemozhetbyt]

Checklist

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

This is the same tricky case as described in #19913, I've somehow missed it then.

Too common link reference in cli.md corrupts heading from string_decoder.md in assembled all.html (markdown references seem to be case-insensitive).

Compare: stringDecoder.end([buffer]) in string_decoder.html and stringDecoder.end(buffer) in all.html with buffer parameter made mandatory and linkified.

I've checked all the headings in all.html for any additional child HTML elements except expected (code and span with # TOC links) and found only this anomaly plus nits addressed in #20086. So, for now, there are no more similar issues.

However, I do not know how we can prevent this false linkification and parameter corruption in the future. I can think of these options at least:

• Escape all the [] in headings and demand this from now on by a rule. This may be a huge churn PR and a hard rule to follow unless added in doc linting.
• Make a doc linting rule to compare all the link references in all docs with parameters in all headings in all docs and warn about collisions. I do not know if this is implementable and performance-safe.
• Forbid tools/doc/html.js from adding any links to headings except for # TOC links.

cc @nodejs/documentation to consider this.

Also in passing:

• Fix sort nit in bottom references.
• Make the Buffer link refer to Buffer class instead of the top module heading.

[vsemozhetbyt]

Please, add 👍 here to approve fast-tracking.

[vsemozhetbyt]

CI-lite: https://ci.nodejs.org/job/node-test-pull-request-lite/538/

[vsemozhetbyt]

Landed in 5eb9f3c