Deprecate minConcurrency in Crawler options, replace it with desiredConcurrency

[metalwarrior665]

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

@crawlee/basic (BasicCrawler)

Issue description

minConcurrency is a dangerous option and desiredConcurrency is almost always a better option. The problem is minConcurrency is option on crawler level while desiredConcurrrency is not so users will naturally tend to use the former.

So I would deprecate it and leave it only in autoscaledPool while I would put desired on crawler level as it is useful.

One side-note is that desiredConcurrency is not a great name as it only affects where it starts. Something like initialConcurrency would be better so we could go for rename with deprecation as well.

Code sample

No response

Package version

any

Node.js version

any

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

[B4nan]

I like the proposal for renaming to initialConcurrency, we could rename it right ahead while keeping the old name for BC and clean this up in next major. Btw the minConcurrency is taken into account only when downscaling, that's the confusing part, right? The example in docs seems to be also incorrect (the comment above minConcurrency).

https://crawlee.dev/docs/guides/scaling-crawlers#minconcurrency-and-maxconcurrency