fix: batch Gateway Connector target scans

[aidandaly24]

Summary

• scan Gateway Targets in service-max 1000-item batches when building logical Connector pages
• replay only the exact Target prefix needed when a scan contains Connector overflow, preserving AWS pagination tokens without custom cursor state
• treat the 101-scan limit as a request safety cap rather than tying it to the adjustable default Target quota

Follow-up to #1956, addressing the late review comments about raised Target quotas and one-request-per-Target behavior with --max-results 1.

Testing

• bun test src/core/gateway.test.ts src/handlers/gateway/gateway.fixture.test.tsx (22 pass)
• bun run typecheck
• bun run lint:check
• bun run format:check
• bun run build
• bun test src (1100 pass; 7 unchanged local src/io/exec.test.ts process-runner failures on files identical to refactor)

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.94%. Comparing base (5e03551) to head (33b3459).
⚠️ Report is 1 commits behind head on refactor.

Additional details and impacted files

@@            Coverage Diff            @@
##           refactor    #1979   +/-   ##
=========================================
  Coverage     96.94%   96.94%           
=========================================
  Files           325      325           
  Lines         17869    17884   +15     
=========================================
+ Hits          17323    17338   +15     
  Misses          546      546           

☔ View full report in Codecov by Harness.
📢 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.

[notgitika]

thanks for addressing it!

[notgitika]

nit: maxResults should be validated as an integer from 1–1000. currently 0, -1 or 1.25 is being accepted