requestHandlerTimeoutSecs upper-bound overflows

[metalwarrior665]

Which package is this bug report for? If unsure which one to select, leave blank

@crawlee/basic (BasicCrawler)

Issue description

WARN  PlaywrightCrawler: requestHandlerTimeoutMillis 100000000070000does not fit a signed 32-bit integer. Limiting the value to 2147483647
INFO  PlaywrightCrawler: Starting the crawl
(node:22406) TimeoutOverflowWarning: 200000000140000 does not fit into a 32-bit signed integer.
Timeout duration was set to 1.

This was fixed in the past by setting it to 2147483647 but seems Crawlee now multiplies this so we overflow again.

Code sample

requestHandlerTimeoutSecs: 10000000000

### Package version

latest

### Node.js version

node 16

### Operating system

_No response_

### Apify platform

- [ ] Tick me if you encountered this issue on the Apify platform

### I have tested this on the `next` release

_No response_

### Other context

_No response_

[metalwarrior665]

Even if you set requestHandlerTimeoutSecs: 2000000 (which is bellow safe signed int / 1000), it still fails a bit later so it is again multiplied somewhere.

(node:22706) TimeoutOverflowWarning: 4000140000 does not fit into a 32-bit signed integer.
Timeout duration was set to 1.

[foxt451]

This PR would handle this: #1981. However, @B4nan mentioned it would be a good idea to allow to opt out of timeouts altogether, so I think this issue will be up to discussion