`JSDOMCrawler` and `LinkeDOMCrawler` never passed the context-bound
`enqueueLinks` into their enqueue-links helpers (unlike
`CheerioCrawler`), so links were enqueued straight into the request
queue and skipped the crawl depth tracking in `BasicCrawler`.
`maxCrawlDepth` has therefore had no effect for these two crawlers since
it shipped in v3.14.0. Both files already had the
`BoundEnqueueLinksInternalOptions` machinery, it just was never reached.
This wires it up the same way `CheerioCrawler` does, including the
`limit` pre-clamp removal from #3927, which applies once the bound path
is taken.
Added crawl depth tests for both crawlers, mirroring the existing
`CheerioCrawler` coverage.
Replaces #4020, which targeted v4; the bug exists on v3 as well, so the
fix lands here instead.
Martin Adámek
4d34aeab6d