DOC See Also descriptions do not match for multiple functions/classes

### Describe the issue linked to the documentation

While working on a docstring-related pull request (#24259) I noticed that, sometimes, the See Also description for the same function/class does not match. For instance, the `accuracy_score` description was different depending on the class I looked at:

https://github.com/scikit-learn/scikit-learn/blob/feaf3829969b640594a145029e3adcffd2db0999/sklearn/metrics/_classification.py#L745-L747
https://github.com/scikit-learn/scikit-learn/blob/feaf3829969b640594a145029e3adcffd2db0999/sklearn/metrics/_classification.py#L956-L960

I decided to [investigate it further and see if it was occuring elsewhere (click here to check the gist where I regexed the raw files)](https://gist.github.com/vitaliset/07ccccb0364b6eaa0f73c5e936d54756). Today, at commit [2f8b8e7f1](https://github.com/scikit-learn/scikit-learn/commit/2f8b8e7f1), we have 56 functions/classes that have some sort of different descriptions at some See Also. From looking at them at first glance I have sorted the differences I get into 4 categorys:

1. Those where the description is related to the current class/function;
    - For instance, inside the `RegressorChain` class, `ClassifierChain` is described as the "equivalent" version. That is a different description from the one we see inside `MultiOutputClassifier`, but inside the context of the `RegressorChain` class, it makes sense.
https://github.com/scikit-learn/scikit-learn/blob/2f8b8e7f1aa628289b92cfc5bdfc7907688962b1/sklearn/multioutput.py#L965-L967

2. Those related to extra "\n" on the text;
https://github.com/scikit-learn/scikit-learn/blob/2f8b8e7f1aa628289b92cfc5bdfc7907688962b1/sklearn/kernel_approximation.py#L106
https://github.com/scikit-learn/scikit-learn/blob/2f8b8e7f1aa628289b92cfc5bdfc7907688962b1/sklearn/kernel_approximation.py#L292-L293

3. Those that are different per se;
    - For instance, the `accuracy_score` descriptions we mentioned earlier have no obvious reason to be different.

4. Those that are related to the docstring pattern.
    - For instance, we are missing a space after the name of the class/function being referenced. So my script puts it inside the previous description (_extra question: shouldn't it be failing on the numpy doc validation? I was excepting it to be an open docstring from #21350, but this function was already done by #24351_).
https://github.com/scikit-learn/scikit-learn/blob/2f8b8e7f1aa628289b92cfc5bdfc7907688962b1/sklearn/metrics/_ranking.py#L961

### Suggest a potential alternative/fix

I was planning on taking a closer look at [the output table I get with the differences in the descriptions](https://gist.github.com/vitaliset/07ccccb0364b6eaa0f73c5e936d54756) and coming up with the list of functions/classes that we should change to make it uniform across different occurrences of See Also.
Then, as this is a fairly beginner friendly issue, I would edit the issue description and give it a step-by-step (copying most part of what @thomasjpfan did in [#21350](https://github.com/scikit-learn/scikit-learn/issues/21350)) and let folks looking for a "good first issue" help. I would be happy to make sure the task bullets are up to date.

What do the maintainers think? Does it make sense? :)

_PS: Of course, we will be forever vulnerable to this kind of issue if we don't create a test (maybe adapted from my [gist](https://gist.github.com/vitaliset/07ccccb0364b6eaa0f73c5e936d54756)). The problem here is that sometimes it just makes sense to have different descriptions... We can create an "ignore list" maybe, but we can discuss this later._

COMMENT:
Thanks for the comment @glemaitre! I made a small pull request related to some doc typos I found here and will close this issue.

If someone does decide to solve this minor issue in the future, one can use the [gist](https://gist.github.com/vitaliset/07ccccb0364b6eaa0f73c5e936d54756) to find the mismatches and fix them quickly.

Labels: Documentation