Skip Symfony-only rules that would misfire on Laravel projects

[TomasVotruba]

Why

Most Symfony rules already self-scope: they gate on Symfony base classes, interfaces, attributes or Symfony\/Doctrine\ type prefixes, so on a non-Symfony project (e.g. Laravel) they never fire.

Four rules did not self-gate and could misfire on plain PHP / Laravel classes:

• NoConstructorAndRequiredTogetherRule - only checks __construct() + @required doc tag
• NoListenerWithoutContractRule - triggers on any class named *Listener
• NoNullableServiceInConstructorRule - triggers on any nullable constructor dependency
• NoServiceJugglingRule - triggers on autowire* method naming

What

Adds LaravelPresenceResolver, which detects a Laravel project via ReflectionProvider->hasClass('Illuminate\Foundation\Application') (ReflectionProvider over class_exists, per the repo's own rule). The four rules early-return when Laravel is present.

Behavior on non-Laravel projects is unchanged - plain PHP libraries keep these rules. Only a project with Laravel installed skips them.

Tests

• New LaravelPresenceResolverTest
• Existing fixture tests for the four rules still pass (Laravel absent -> guard inert)
• Full suite green, plus ECS, Rector, PHPStan