…e TestsListener (fancyweb)This PR was merged into the 5.1 branch.Discussion----------[PhpUnitBridge] Fix Deprecation file when it comes from the TestsListener| Q             | A| ------------- | ---| Branch?       | 5.1| Bug fix?      | yes| New feature?  | no| Deprecations? | no| Tickets       | -| License       | MIT| Doc PR        | -#38031 caused an unwanted regression: if the frame `class` matches `SymfonyTestsListenerFor` it used to always return, now it continues so the `originClass` and `originMethod` properties are set. Therefore, the deprecation is considered as coming from the test listener. It ends up in the "legacy" group and muted because the test listeners contains the word "Legacy" in their namespaces.Example test:```php<?phpnamespace App\Tests;use PHPUnit\Framework\TestCase;use Symfony\Component\EventDispatcher\DependencyInjection\ExtractingEventDispatcher;final class FooTest extends TestCase{    public function test(): void    {        // ExtractingEventDispatcher is@internal        new class extends ExtractingEventDispatcher {};        $this->assertTrue(true);    }}```On 4.4:```Other deprecation notices (1)  1x: The "Symfony\Component\EventDispatcher\DependencyInjection\ExtractingEventDispatcher" class is considered internal. It may change without further notice. You should not use it from "Symfony\Component\EventDispatcher\DependencyInjection\ExtractingEventDispatcher@anonymous".```On 5.1:```Legacy deprecation notices (1)```Commits-------1ba06a0 [PhpUnitBridge] Fix Deprecation file when it comes from the TestsListener