feat: accept an AbortSignal in resource-client methods

[vdusek]

Every method that takes timeoutSecs now also takes signal?: AbortSignal, and forwards it to each request it sends. Once the signal aborts, the request in flight ends, no retry or further poll follows, and the method rejects with the signal's reason. The field sits on TimeoutOptions, so call(), waitForFinish() and the single-request methods all pick it up.

• The signal never reaches the query string or the body. Methods that spread their remaining options into the params or the getOrCreate() body take it out first.
• The waits between polls and between batchAddRequests() retries end early on abort. sleep(ms, signal) moved from the HTTP client into utils.ts for that.
• batchAddRequests() rejects on abort. Its catch otherwise reports the remaining requests as unprocessed and resolves.
• StreamedLog takes a signal, which call() passes through. Without it, call() with the default log redirection hung after an abort until a quiet run printed its next line.
• The timeouts concept page has a new "Aborting a call" section.

Tests: a forwarding case for every method in the client_timeouts table, and abort_signal.test.ts, which drives call(), waitForFinish() and batchAddRequests() against a local server.

Closes #1071

✍️ Drafted by Claude Code

[github-actions]

⚠️ There are broken links in the documentation.

See more at https://github.com/apify/apify-client-js/actions/runs/36116203177#summary-108010787689