[all components][docs-infra] Update all error messages to have docs page?

[oliviertassinari]

Summary

I'm creating this issue to talk about having a great execution for error DX, as well as normalization between the repositories, as there is nothing specific to any context, whatever is best in class would applied to React docs, Next.js docs, etc.

Have links

• Go to each error and see if links can't be created.

Examples:

• Next.js. Their Head of docs created this PR: Adds consistency to ESLint rules. vercel/next.js#34335 which seems to be great.
  However, it feels very broken to force custom pages for every error. You can have a permalink (/r/ URLs) to the right place of the docs instead for this, as well as trivial errors that don't need a docs page. It's duplication of content. So our policy could be to have docs about the error when needed, and avoid custom pages, e.g. https://nextjs.org/docs/messages/get-initial-props-export as much as possible.
• Sentry has created content for MUI X Data Grid: https://sentry.io/answers/the-data-grid-component-requires-all-rows-to-have-a-unique-id-property/. (I found this with the recurring SEO health checks). I guess it's because a lot of Sentry clients logs this error. We already document this in the docs, it looks like we are missing a link from the error to the docs.

Force permalink

• Eslint rule to force the link from errors to be a /r/ and never plain.

Examples:

• Next.js. All seems to point to https://nextjs.org/docs/messages/. https://github.com/search?q=repo%3Avercel%2Fnext.js+%22const+url+%3D+%27https%3A%2F%2F%22&type=code&p=2

Force error message format

• Ensure all errors have the right clear structure: https://www.notion.so/mui-org/Technical-writing-style-guide-7e55b517ac2e489a9ddb6d0f6dd765de?source=copy_link#85219822c3194b6f8a49ee08ea82b90a

Search keywords: -