[docs][i18n] Figure out what to do with remaining relative MDX imports

[tesseralis]

Description

Follow-up of #20685

Now that the major components have been taken care of, there are still some pages that use one-off components that require relative imports:

• graphql-api.md: Uses APIReference and GraphqlApiQuery to pull in API references.
  • Issue: (docs) Consider moving/removing fragments section of GraphQL API #21109
• data-fetching.md: Uses two examples built just for the page.
  • Issue: [docs][i18n] Replace live examples docs/data-fetching with a CodeSandbox <iframe> #21112
• docs-and-website-components: Pulls in Breadcrumb and TableOfContents to show them as examples (even though these components aren't intended to be used in MDX docs)
  • PR: docs: move Breadcrumb and ToC component docs for i18n efforts #20913
• blog/100-days.md: Uses a custom <EmailCaptureForm100Days/> component that really should just be the normal email capture form.
  • PR: Replace custom 100days email component with normal EmailCaptureForm #21288

For now, we can just exclude those files from being pulled in, and in the worst case scenario, just add them globally as well.

[tesseralis]

Interesting to note: Docusaurus V2 also runs into this same problem with regard to versioning. Relative links in MDX don't work on versioned docs because they're in a different relative directory (much like translated docs).

Their solution to this is to use an alias. This seems like it might be a potential solution? While using path aliases in general can lead to havok, this would be a pretty limited use case for them (only used to reference www components from the docs).