fix: Correct inverted return value in Scrapy scheduler enqueue_request

[vdusek]

Summary

• The enqueue_request method in ApifyScheduler was returning bool(result.was_already_present), which incorrectly returned True for duplicates and False for newly enqueued requests
• Per Scrapy's BaseScheduler contract, enqueue_request should return True when the request was successfully stored (new) and False when rejected (duplicate)
  • See https://docs.scrapy.org/en/latest/topics/scheduler.html#scrapy.core.scheduler.BaseScheduler.enqueue_request
• One-line fix: return not bool(result.was_already_present)

Test plan

• CI passes

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

[codecov]

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 85.50%. Comparing base (252eb4e) to head (6fe6898).

Files with missing lines	Patch %	Lines
src/apify/scrapy/scheduler.py	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #794      +/-   ##
==========================================
+ Coverage   85.46%   85.50%   +0.03%     
==========================================
  Files          46       46              
  Lines        2697     2697              
==========================================
+ Hits         2305     2306       +1     
+ Misses        392      391       -1     

Flag	Coverage Δ
e2e	35.40% <0.00%> (ø)
integration	57.50% <0.00%> (+0.03%)	⬆️
unit	72.45% <0.00%> (ø)

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.