allow consecutive newlines in jsdoc tag comments

[michens]

Fixes #35511

The parser for JSDoc tag comments currently skips successive NewLineTrivia tokens.
In files using CRLF line endings, this leads to only \r being retained in the node, which can cause issues for tooling.
This PR removes that restriction, such that all NewLineTrivia tokens are persisted in the node.

[sandersn]

This is probably a good change, but it's not the correct fix for #35511 — the jsdoc scanner should treat \r\n as a single newline, but doesn't. #39351 addresses that.

However, skipping successive newlines doesn't make too much sense to me since JSDoc is generally pretty sensitive to whitespace, so I think it's a good idea get rid of the rule.

I approved the PR, but can you please merge from master after #39351 is in? I can do it when I have the chance if you don't want to switch back to this PR.

[michens]

This has been merged with master after your changes.

[andrewbranch]

@typescript-bot pack this

[typescript-bot]

Heya @andrewbranch, I've started to run the tarball bundle task on this PR at 1cbf239. You can monitor the build here.

[typescript-bot]

Hey @andrewbranch, I've packed this into an installable tgz. You can install it for testing by referencing it in your package.json like so:

{
    "devDependencies": {
        "typescript": "https://typescript.visualstudio.com/cf7ac146-d525-443c-b23c-0d58337efebc/_apis/build/builds/78496/artifacts?artifactName=tgz&fileId=C928C1027B0D36A39755BE621DF82E17C9EC9855604949D4070B3B55674587C202&fileName=/typescript-4.0.0-insiders.20200702.tgz"
    }
}

and then running npm install.

[typescript-bot]

Hey @andrewbranch, something went wrong when looking for the build artifact. (You can check the log here).