add script for running markdownlint locally

[gregwebs]

note that I created a file mdlint.json that matches what is described as
what we use in docs-cn

Also use that configuration in the CI

[yikeke]

Hi Greg, I have no expertise in this area, so I'm gonna ask some pretty simple questions. Can you explain a little more about why we need to run markdownlint locally (since we already have the markdownlint CI check in the docs repo) and what has changed or what we do exactly after using the script you gave? @gregwebs

[gregwebs]

@yikeke you don't need to run it locally. You can wait for the CI if you like. This is also stated in the new CONTRIBUTING.md file.

[gregwebs]

@cofyc this is for running locally, not CI. But I changed both to install a specific version and the script will remove the package-lock.json if it created it.

[yikeke]

@yikeke you don't need to run it locally. You can wait for the CI if you like. This is also stated in the new CONTRIBUTING.md file.

Yeah saw it. Thanks~ This could be helpful!

[yikeke]

@cofyc this is for running locally, not CI. But I changed both to install a specific version and the script will remove the package-lock.json if it created it.

The original script that added markdown lint check into CI was given by @aylei in #1406. Also in docs-cn: pingcap/docs-cn#1494. (See Jira Issue)

Please take a look at the change proposed by Greg, thanks~ @aylei

[gregwebs]

some linter errors are showing up in other files now, but I don't know why: I would have expected it to show up on the prior commit also.

[aylei]

LGTM