Update markdown-lint-check to v3.10.0.

[creachadair]

This version includes a fix for #anchor links.
See tcort/markdown-link-check#91.

[creachadair]

Hi, @gaurav-nelson! I realized after creating this PR that someone else already has one open to do the same thing (cf. #129). Is there anything I can do to help test this change?

[gaurav-nelson]

Thank you @creachadair I guess I'll have to close this one and use #129 as it was the first one. Last time when I upgraded to 3.9.3 (#126) I received a bit of issues. PS: #127

So this time I want to check fork and test those repos locally, before merging and releasing. You can definitely help by maybe:

• Cloning those repos locally and checking the output with the updated MLC version.
• Paste the output in gist and comment on 129 with link to gist.

Let me know if you can help with that.

[creachadair]

So this time I want to check fork and test those repos locally, before merging and releasing.

Makes sense. I'll give this a try and post a note here when I've got some data to show.

Thanks!

[creachadair]

Per the above, I did a before/after test, and the results are below. In short, this patch appears to fix the primary issue with #anchor links.

Repro Outline

1. Fork the target repository and enable actions.
2. Edit the link-checker actions config to use 1.0.14.
3. Run the action and verify that errors similar to those reported occur.
4. Edit the link-checker actions config to use a patch targeting v3.10.0.
5. Run the action and verify that those errors are absent.

To effect the patch in step (4), I forked this repository and applied the diff from this PR, then updated the actions config to point to my fork instead of the real one.

Result

• Repository: https://github.com/tendermint/tendermint (forked at creachadair/tendermint)
• Logs from step (3): https://gist.github.com/0e44b6c43c100741fd6ec91cf8b6ffec
• Logs from step (5): https://gist.github.com/01b696644661b0b046ca58cd311f34be

Errors before patch: 408
Errors after patch: 32

[creachadair]

Hi @gaurav-nelson, I wanted to check back in whether there are any further data you'd like to see before you'd feel comfortable merging the update in #129.