[Feat] [firecrawl-py] Add support for controlling retry behaviour in `FirecrawlApp` and `AsyncFirecrawlApp`

[m-roberts]

Problem Description
It would be nice to have more control over retry logic. Currently, the internal methods use this, but they are not available to extract, etc.

Proposed Feature
Add these as optional parameters to top-level functions, or as constructor parameters to allow for more precise control.

Alternatives Considered
Not sure that an alternative is required.

Implementation Suggestions
Both approaches would suit my needs, though a thorough implementation would support both, opting to take those passed into the method invocations over the defaults.

Use Case
For me, this is particularly useful when developing a prompt and response structure against a dataset, which requires many calls - however, I think this would be useful in any case where there's a spike in traffic that may require more control over retry behavior.

[nickscamara]

@m-roberts Great suggestion, makes sense! Thank you!