Markdown html comment parsing error if there is a trailing space

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[ ] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description

Html comment in markdown files raises a syntax error if there is a trailing space. For example, the markdown code:  raises an error but  doesn't.

Reproducible demo

https://github.com/Conflux-Chain/conflux-documentation/tree/l10n_translation-pipeline

Steps to reproduce

The error could be reproduced by using the demo in Github codespace. You can simply run yarn zh. Or:

open a project with a existed markdown file

add the following content to the tail of any markdown file

<!-- ![blabla.png](/img/blabla.png)-->
<!-- ![blabla.png](/img/blabla.png)--> 
<!-- ![blabla.png](/img/blabla.png)-->

Note: there is a trailing space for the second line

run the project, then the error should be like: Noting that the first and third line will be successfully parsed
remove the trailing space of the second line
the error disappears

Expected behavior

The html comment with a trailing space is expected to be parsed successfully.
If this is hard to accomplish, at least the right error should be raised but not an "unexpected token" error

Actual behavior

I am integrating my project with Crowdin to the i18n. The default strategy of Crowdin would convert the trailing \n to a space in certain circumstances. So this is the source doc and here is an auto-generated untranslated file by Crowdin.

The command yarn start --locale zh-Hans but the compilation fails. Although Crowdin slightly changes the structure of the original file, I think it is acceptable because other tools, like vs code, won't raise an error. As far as I am concerned, this might be a bug of docusaurus or its markdown parsing engine. (This is not the actual error, but is exactly same except for line number)

Your environment

Public source code:https://github.com/Conflux-Chain/conflux-documentation/tree/l10n_translation-pipeline
Public site URL:
Docusaurus version used:2.3.1
Environment name and version (e.g. Chrome 89, Node.js 16.4): node.js v16.16.0
Operating system and version (e.g. Ubuntu 20.04.2 LTS): macOS 12.6

Self-service

[ ] I'd be willing to fix this bug myself.

facebook / docusaurus