test: extend retry window for synthetic PPE event propagation

[vdusek]

Summary

• Increased retry_counter(30) to retry_counter(120) in test_actor_push_data_charges_both_events and test_actor_push_data_combined_budget_limit
• Synthetic events like apify-default-dataset-item are computed by the platform from dataset writes asynchronously — unlike explicit charges (which hit the charge endpoint directly and reflect immediately), these take longer to propagate into charged_event_counts
• The existing 30-second window was insufficient; 2 minutes gives the platform enough time

Failed CI run that triggered this fix:

• https://github.com/apify/apify-sdk-python/actions/runs/24509008169/job/71634833762?pr=863

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.64%. Comparing base (390ccaf) to head (21c6515).
⚠️ Report is 4 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #865      +/-   ##
==========================================
+ Coverage   86.57%   86.64%   +0.06%     
==========================================
  Files          48       48              
  Lines        2920     2920              
==========================================
+ Hits         2528     2530       +2     
+ Misses        392      390       -2     

Flag	Coverage Δ
e2e	37.87% <ø> (ø)
integration	59.28% <ø> (ø)
unit	74.69% <ø> (+0.06%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 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.