chore: Swap Markdownlint for remark-lint

[nschonni]

Re-opening #2460 because GitHub closed it on a force-push

[XhmikosR]

I'm definitely in favor of this assuming nodejs/remark-preset-lint-node#21 lands, released and this PR makes the minimum possible overwrites.

The more closer we are to the upstream rules there better. My main concern is the different markdown renderer we use here, but hopefully it won't cause any issues.

[XhmikosR]

@nschonni are the current rules the minimum needed ones? Do we cover most of what we covered before?

Also, I wonder, does remark-lint have a cache feature?

[nschonni]

I don't think this actually covers everything that Markdownlint does, but it has some more that it doesn't. A PR landed to added the "recommended" preset to the node baseline, but it needs a new release to include it.
Not sure what you mean by caching in this case

[Trott]

A PR landed to added the "recommended" preset to the node baseline, but it needs a new release to include it.

Would it be useful for me to publish a release at this time?

[nschonni]

Sure, maybe land the other minor dependency cleanup one first though.

[nschonni]

For now, I've submitted a few PRs so some of the rules can be re-enabled

[Trott]

Sure, maybe land the other minor dependency cleanup one first though.

Published.

[nschonni]

Thanks, bumped the package and disabled newly failing rules

[XhmikosR]

Re: caching, I meant like stylelint or eslint has, so that consequent runs are faster. Maybe it doesn't have this feature, no big deal for now.

So, to summarize:

1. I personally care about covering most of the things we covered before
2. We need to get the suppressions as close to zero eventually

That being said, this shouldn't block us from merging this. We can tackle the rules as we go.

[MylesBorins]

RSLGTM

[Trott]

Are we good to land this once we bump to 1.10.1?

[nschonni]

I think so, I've re-installed and rebased