fix(theme): add more tag names to inline code element set

[Josh-Cena]

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 Inconsistent display when b, i, s, or u tags are used within code tags #8189) and the maintainers have approved on my working plan.

Motivation

I should have done this initially but was too lazy to. This list is adapted from https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Content_categories#phrasing_content

Test Plan

Test links

Deploy preview: https://deploy-preview-_____--docusaurus-2.netlify.app/

Related issues/PRs

[netlify]

✅ [V2]

Name	Link
🔨 Latest commit	8b97b3a
🔍 Latest deploy log	https://app.netlify.com/sites/docusaurus-2/deploys/6340d55d186e0800092833a0
😎 Deploy Preview	https://deploy-preview-8190--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 settings.

[github-actions]

⚡️ Lighthouse report for the deploy preview of this PR

URL	Performance	Accessibility	Best Practices	SEO	PWA	Report
/	🟠 84	🟢 98	🟢 100	🟢 100	🟠 80	Report
/docs/installation	🟠 86	🟢 100	🟢 100	🟢 100	🟢 90	Report

[github-actions]

Size Change: 0 B

Total Size: 816 kB

ℹ️ View Unchanged

Filename	Size
website/.docusaurus/globalData.json	52.4 kB
website/build/assets/css/styles.********.css	112 kB
website/build/assets/js/main.********.js	611 kB
website/build/index.html	40.9 kB

_{compressed-size-action}

[slorber]

LGTM 👍 thanks

Just to remember the context, is this only useful when using <code> tags in mdx?

like heyheyhey ? 🤪

[Josh-Cena]

Just to remember the context, is this only useful when using <code> tags in mdx?

Yep, which is why I still excluded some non-typographic tags. Bundle size phobia. Let's hope no one complains.

[slorber]

For reference, with MDX 2.0 (PR: #8288) all the lower-case JSX elements (like <code> will not be swaped by our own <Code> theme component

This is now your responsibility to create/import your own Code component in case the default behavior of MDX 2.0 is not good for your use case. I think it should be good in most cases as it's just rendering the dom nodes as is, like the web behaves.

The theme MDXComponents/Code component will only be used when using fenced code blocks (that's a design decision of MDX 2).

I'm removing the code to render elements inline anyway because fanced code blocks are never rendered inline.

This if/else logic was added only to mitigate the fact it was not easy to distinguish between fenced code blocks and usage of <code> through JSX, so that seems safe to remove