[docs] Fix internal link to valueParser

[alexfauquette]

Fix #5176

[mui-bot]

These are the results for the performance tests:

Test case	Unit	Min	Max	Median	Mean	σ
Filter 100k rows	ms	288.5	513	446.1	414.08	76.849
Sort 100k rows	ms	578.5	1,065	771.8	854.54	169.667
Select 100k rows	ms	141.1	295.7	220.4	220.02	55.254
Deselect 100k rows	ms	111.2	241.1	146.7	173.64	52.069

Generated by 🚫 dangerJS against 0ddc502

[oliviertassinari]

I think that it's a bit confusing. We say, use the value parser to implement customer filtering input value parser

and then link people to a different feature: edition, which is not filtering.

Maybe it would make sense to have the same section in the documentation as https://mui.com/x/react-data-grid/filtering/#parsing-values but for the column filtering.

[alexfauquette]

I remind that during the first months, I found parser, getter, formatted and setter quite confusing and open #3215

What would you think about a dedicated page for them to provide an overview of how data is transformed like proposed in #3215 ?

[oliviertassinari]

Flavien had commented a bit on this problem in #4956 (comment). I guess the demo in https://mui.com/x/react-data-grid/column-definition/#value-formatter is a good illustration of the need for valueParser. When you search for 20 you get no results 🙃. Link it here

The chart #3215 (comment) helps understand how this works 👍 . It could help to have documentation about it. The tricky part might be, how do we have developers find it when they need it?