[DomCrawler] prevent deprecation being triggered from assertion

[xabbuh]

Q	A
Branch?	4.4
Bug fix?	yes
New feature?	no
Deprecations?	no
Tickets	Fix #35889
License	MIT
Doc PR

[fancyweb]

As pointed in the issue, don't we need to also update https://github.com/symfony/dom-crawler/blob/4.4/Test/Constraint/CrawlerSelectorTextSame.php#L48?

[xabbuh]

@fancyweb Indeed, I fixed it.

[fabpot]

Thank you @xabbuh.

[flaushi]

Maybe we could add a hint to assertSelectorTextSame into the error message

symfony/src/Symfony/Component/DomCrawler/Crawler.php

Line 619 in 15edfd3

@trigger_error(sprintf('"%s()" will normalize whitespaces by default in Symfony 5.0, set the second "$normalizeWhitespace" argument to false to retrieve the non-normalized version of the text.', __METHOD__), E_USER_DEPRECATED);

? I think many people had to research this issue

[xabbuh]

What issue would that solve?

[flaushi]

I can imagine may people using $crawler->text() in their tests.

They all have to read through this issue and PR to finally see that there is a new assertion assertSelectorTextSame they can use to prevent the deprecation error. Kind of "documentation in issue"