fix(mdx-loader): allow image paths to be URL encoded

[Josh-Cena]

Motivation

Fix #6791

Have you read the Contributing Guidelines on pull requests?

Yes

Test Plan

Added unit tests; https://deploy-preview-6792--docusaurus-2.netlify.app/tests/docs/tests/img-tests/

[netlify]

✔️ [V2]

🔨 Explore the source changes: 7a220bb

🔍 Inspect the deploy log: https://app.netlify.com/sites/docusaurus-2/deploys/621df6960cbf840008c994a9

😎 Browse the preview: https://deploy-preview-6792--docusaurus-2.netlify.app

[github-actions]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🟠 Performance	52
🟢 Accessibility	100
🟢 Best practices	92
🟢 SEO	100
🟢 PWA	90

Lighthouse ran on https://deploy-preview-6792--docusaurus-2.netlify.app/

[github-actions]

Size Change: 0 B

Total Size: 789 kB

ℹ️ View Unchanged

Filename	Size
website/.docusaurus/globalData.json	49.7 kB
website/build/assets/css/styles.********.css	106 kB
website/build/assets/js/main.********.js	596 kB
website/build/index.html	37.6 kB

_{compressed-size-action}

[slorber]

Thanks 👍

[ryh]

But there are rare case files named with url encoded in file system.
I did not test on Github pages, but marktext.app won't recognize those.

[Josh-Cena]

@ryh But why?🤷‍♂️ Where're the images coming from? How much effort would it be to correct those image paths?

marktext.app won't recognize those.

Does that mean that at least we are in line with the behavior of Mark Text? I tested on Typora and it seems to be unhappy with either ![](./foo%202.png) or ![](./foo 2.png) when the file is literally called foo%202.png. I don't think we should do anything, since in this case, you are supposed to double-encode your path, e.g. ![](./foo%25202.png)