[Link] Improve TypeScript integration with react-router

[pachuka]

• I have followed (at least) the PR section of the contributing guide.

Closes #15105, closes #15299, based on 3rd suggestion in #15299 (comment)

Since TypographyProps is currently not using OverridableComponent yet, I omitted the 'Component' prop for now to avoid conflicting types.

[mui-pr-bot]

No bundle size changes comparing 1bff0f7...cb3c1b9

Generated by 🚫 dangerJS against cb3c1b9

[eps1lon]

Feel free to create a Link.spec.tsx. Would be nice to have some tests for integration with react-router-dom.

[oliviertassinari]

Nice, an integration test would be great. Ideally, I would add a live demo in https://next.material-ui.com/style/links/#third-party-routing-library. We might already have one demo for the buttons, we can copy.

[oliviertassinari]

I have added a live demo for the link, like @eps1lon did for the button. We should be good to go.

[pachuka]

@oliviertassinari - you beat me to it! Just a quick question, when I was looking at other places that react-router-dom is used in the docs such as docs/src/pages/demos/breadcrumbs/RouterBreadcrumbs.js the Router is wrapped in a <NoSsr> component with the following comment: // Use NoSsr to avoid SEO issues with the documentation website. Do we need to do that here as well?

[oliviertassinari]

@pachuka Good question. The NoSsr is more a hack than a good solution (Google Bot can still see it with its JavaScript rendering engine). I have solved the problem by using URLs that exist in the documentation. I want to avoid linking 404.