feat(core): throw error when official docusaurus dependencies use different versions

[JorensM]

Pre-flight checklist

• I have read the Contributing Guidelines on pull requests.
• If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
• If this is a new API or substantial change: the PR has an accompanying issue (closes Strict check for plugin version mismatch #9342 ) and the maintainers have approved on my working plan.

Motivation

Test Plan

Related issues/PRs

#9342

[Josh-Cena]

Please, check for existing PRs before sending one. #9380

[Josh-Cena]

Sorry, I see you actually claimed the issue first!

[Josh-Cena]

Could you respect the PR template? Most importantly it asks you to link to the issue to intend to address because it will be automatically closed if you include text like "closes #xxxx".

[JorensM]

@Josh-Cena Thanks for noticing haha. But if you think the other PR is better in some way, you can merge that one. Also I was using Gitpod to make this PR, and I think there should've been some extra info in the PR description that I should've added like a checklist.

[netlify]

✅ [V2]

Name	Link
🔨 Latest commit	cc7fdd4
🔍 Latest deploy log	https://app.netlify.com/sites/docusaurus-2/deploys/6522d910e10bc100088dcdef
😎 Deploy Preview	https://deploy-preview-9381--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
/	🟠 87	🟢 97	🟢 92	🟢 100	🟠 89	Report
/docs/installation	🟠 80	🟢 98	🟢 92	🟢 100	🟠 89	Report

[JorensM]

@Josh-Cena The tests seem to have failed, but I'm not sure why. Could you take a look and explain why they're not passing?

[Josh-Cena]

The test logs are public and you can click on them. For example: https://github.com/facebook/docusaurus/actions/runs/6445635746/job/17499918105#step:5:1

The reason is because we have a test that expects mismatching plugins to log a message but run completely nontheless, while it now throws an error. You may take inspiration from the other PR to modify the test.

[JorensM]

@Josh-Cena Thanks for explaining! I updated the test

[slorber]

Thanks 👍