tools: host remark-preset-lint-node in-tree

[maclover7]

Moved from https://github.com/watilde/remark-preset-lint-node. The source for this preset will now live in the nodejs/node repository.

Checklist

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

Affected core subsystem(s)

tools

[Trott]

Now that I'm seeing the change set, it makes me want to ask: What's the advantage of doing it this way?

[maclover7]

@Trott main advantages are that there's no need to publish versions on npm or worry about staying up to date with a separate repo -- basically the same deal we have with the docs generator tool.

[BridgeAR]

@nodejs/collaborators thoughts?

[watilde]

Initially, it was an independent private package when I added so we didn't need to worry about the version of the remark-preset-lint-node on npm registry. It might be worth to use the idea again.

• https://github.com/nodejs/node/blob/2e1d092ff18eb0c4274f066ca60c34c85ea71234/tools/remark-preset-lint-node/package.json

Also, it's totally fine to transfer the remark-preset-lint-node repository under @nodejs org if we want :)

// Sorry for my late response!

[mcollina]

LGTM

[maclover7]

@nodejs/collaborators any thoughts? With this the project markdown lint rules will live inside nodejs/node and not in a separate repo. They are already checked into the repo (see the tools/remark-preset-lint-node directory), this just makes it the official source.

[BridgeAR]

Landed in a9e422e

[MylesBorins]

This doesn't land cleanly on LTS. please feel free to backport. Marked as don't land for now