[docs] No more links to component implementations in documentation

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

Summary 💡

In the past, the documentation would have links to the component implementation.
This was really helpful to dig into the code a bit more, especially when designing component style overrides, as the source code is really helpful for this.

I would like to propose reintroducing these links again throughout the documentation and perhaps even having them in a unified location within the docs.

While I understand, that the implementation should not matter for a library to be used, there are often situations where it is still extremely helpful - especially in the cases of style overrides.

The current alternative of always navigating through the source tree on github works as well of course, but is cumbersome and I really miss the simplicity of the links in the past.

Examples 🌈

No response

Motivation 🔦

As described above:

• Simplify looking up the implementation for some components to understand inner workings which are not (or only in rare cases) documented
• Simplify creating style overrides by having easy access to the base implementation

No specific files, tests, or documentation entry points are named. Start by reviewing the current component documentation and source tree to determine how implementation links could be organized; the work is done when the chosen link approach is defined and applied consistently throughout the relevant documentation.