Making campaign actions stats work with manual removal

[JonasLudwig1998]

Q	A
Bug fix? (use the a.b branch)	✔️
New feature/enhancement? (use the a.x branch)	✔️❌
Deprecations?	✔️❌
BC breaks? (use the c.x branch)	✔️❌
Automated tests included?	✔️
Related user documentation PR URL	mautic/user-documentation#...
Related developer documentation PR URL	mautic/developer-documentation-new#...
Issue(s) addressed	Fixes #14761

Description

This PR fixes the issue #14761 and makes sure the campaign action statistics work properly even when manually removing a contact via the change campaigns action

Before the campaign actions of a lead where considered just as 'pending' when the lead was manually removed from a campaign even if the actions where already executed before.

---

📋 Steps to test this PR:

1. Open this PR on Gitpod or pull down for testing locally (see docs on testing PRs here)
2. Create a campaign with an arbitrary action (e.g. update contact) and the change campaigns action in which you remove the contact from the current campaign
3. Run the cron jobs mautic:campaigns:update and mautic:campaigns:trigger
4. Navigate to campaign action stats and check if both actions were registered there as successful

5. Next create a campaign with two update contact actions. The second one should have a delay of 15min before being executed.
6. Run the cron jobs mautic:campaigns:update and mautic:campaigns:trigger
7. Next check the campaign action stats: Here for the first action one successful run should be registered and for the second action one 'pending' should be registered
8. Now remove the contact manually from the campaign

9. Next check the campaign action stats again: For the first action there should be still registered on successful fun. However, for the second action the 'pending' shouldn't exist anymore. So there should be neither a completed action nor a pending action

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 63.67%. Comparing base (0db1736) to head (8fa05ee).
Report is 175 commits behind head on 5.2.

Additional details and impacted files

@@             Coverage Diff              @@
##                5.2   #14809      +/-   ##
============================================
+ Coverage     63.45%   63.67%   +0.21%     
- Complexity    34635    34662      +27     
============================================
  Files          2273     2273              
  Lines        103603   103705     +102     
============================================
+ Hits          65739    66029     +290     
+ Misses        37864    37676     -188     

Files with missing lines	Coverage Δ
...s/CampaignBundle/Controller/CampaignController.php	69.33% <100.00%> (+1.36%)	⬆️
...s/CampaignBundle/Entity/LeadEventLogRepository.php	81.45% <100.00%> (+0.60%)	⬆️
...undles/CampaignBundle/Entity/SummaryRepository.php	95.45% <ø> (ø)

... and 49 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Bastian2718]

Looks good!

[Bastian2718]

Actions do not get Pending status if an Action before is delayed and not executed at that moment. Is it a Bug or should it be like this? (Also before the Patch)