polish(theme): MDX images should use async decoding

[sanjaiyan-dev]

This pull request adds the decoding="async" attribute to the <img /> HTML tag, enhancing image loading performance. This implementation is inspired by the default implementation of the Next.js image component, which prioritizes efficient and fast image loading.

[netlify]

✅ [V2]

Built without sensitive environment variables

Name	Link
🔨 Latest commit	3b00580
🔍 Latest deploy log	https://app.netlify.com/sites/docusaurus-2/deploys/653f541b2c7d63000849b293
😎 Deploy Preview	https://deploy-preview-9470--docusaurus-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions]

⚡️ Lighthouse report for the deploy preview of this PR

URL	Performance	Accessibility	Best Practices	SEO	PWA	Report
/	🟠 60	🟢 97	🟢 100	🟢 100	🟠 89	Report
/docs/installation	🟠 53	🟢 98	🟢 100	🟢 100	🟠 89	Report
/docs/category/getting-started	🟠 68	🟢 100	🟢 100	🟢 90	🟠 89	Report
/blog	🟠 53	🟢 100	🟢 100	🟢 90	🟠 89	Report
/blog/preparing-your-site-for-docusaurus-v3	🟠 54	🟢 97	🟢 100	🟢 100	🟠 89	Report
/blog/tags/release	🟠 87	🟢 100	🟢 100	🟠 80	🟠 89	Report
/blog/tags	🟠 66	🟢 100	🟢 100	🟢 90	🟠 89	Report

[sanjaiyan-dev]

https://nextjs.org/docs/app/api-reference/components/image#other-props

[sanjaiyan-dev]

👀

[slorber]

thanks

I read on the subject and this seems like a reasonable change
Many interesting refs here: https://core.trac.wordpress.org/ticket/53232

Note: this PR took time to merge not because the code was bad, but because you didn't really justify the change and explained the tradeoff. We don't do changes because Next.js use them bindly, we make our own judgement ;)

[sanjaiyan-dev]

thanks

I read on the subject and this seems like a reasonable change Many interesting refs here: https://core.trac.wordpress.org/ticket/53232

Note: this PR took time to merge not because the code was bad, but because you didn't really justify the change and explained the tradeoff. We don't do changes because Next.js use them bindly, we make our own judgement ;)

Welcome, and I apologize for not providing the correct explanation.

[slorber]

Unfortunately this change leads to flakiness in our Argos visual tests (#9805)

I hope we'll not have to revert it

[sanjaiyan-dev]

Unfortunately this change leads to flakiness in our Argos visual tests (#9805)

I hope we'll not have to revert it

Hi @slorber, I am sincerely sorry for the inconvenience. I will do my best to find a solution for this from my side.

[slorber]

no problem, that was worth trying 😄 we'll find a solution