[DeadCode] Skip RemoveDefaultValueFromAssignedPropertyRector on early return in constructor-called method

[TomasVotruba]

RemoveDefaultValueFromAssignedPropertyRector already bails out when the constructor itself contains a return, since the assign can be skipped. But the property may also be assigned in a method called from the constructor - and that method can early return too.

Reported on this real-world case (Mautic Fetcher), where [] was wrongly removed from $unknownLeadIds / $unknownContactIds:

 class Fetcher
 {
-    private array $unknownLeadIds = [];
+    private array $unknownLeadIds;

     public function __construct(...)
     {
         $this->fetchLeads();
     }

     private function fetchLeads(): void
     {
         if (!$campaignMembers = $this->organizer->getLeadIds()) {
             return; // <-- assign never happens, property stays uninitialized
         }

         // ...
         $this->unknownLeadIds = array_values(array_diff($campaignMembers, $this->knownLeadIds));
     }
 }

After the change the whole class is skipped, as fetchLeads() may return before the assign.