tools: update remark-preset-lint-node to v1.3.1

[watilde]

Summary

• Added remark-lint-no-blockquote-without-marker by @Trott and @watilde

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• tests and/or benchmarks are included
• documentation is changed or added
• commit message follows commit guidelines

[nodejs-github-bot]

@watilde build started: https://ci.nodejs.org/blue/organizations/jenkins/node-test-pull-request-lite-pipeline/detail/node-test-pull-request-lite-pipeline/1701/pipeline

[Trott]

There are two .md files with trailing spaces that will need to be fixed before this lands. One is the README and the other is a CHANGELOG file if I recall correctly.

[Trott]

(The fix for the trailing spaces can happen in this PR itself. Probably best as a first commit and then the update of the presets as a second commit.)

[watilde]

I agree. Will arrange the commits and let me ping you when it's done.

[refack]

Code changes LGTM

[refack]

ATM the linter complains only about

README.md
65:18 warning Remove trailing whitespace no-trailing-spaces remark-lint
⚠ 1 warning

[watilde]

I removed trailing whitespace in readme and ci gets green🥗 @Trott

[Trott]

Can you re-arrange the commits so that the doc change is first and the update to the plugin is second? (Or squash them into a single commit, although I prefer them separate for ease of backporting.) The way it is now, make lint fails on the first commit. That could be irksome while bisecting, for example.

[watilde]

This is what I did already :)

Can you re-arrange the commits so that the doc change is first and the update to the plugin is second?

[Trott]

This is what I did already :)

I am easily confused, apparently. :-D

[Trott]

Lite CI: https://ci.nodejs.org/job/node-test-pull-request-lite-pipeline/1705/

[Trott]

Landed in f351c5d...8ce0d4f