Standardize cookie handling

[Mantisus]

Currently we have 3 main cookie handling mechanisms depending on the HTTP client or browser, and none work correctly.

1. HttpxHttpClient.
   This solution is closest to expected. Cookies are stored in Session. However, we use dict which loses the cookie-domain relationship. This can cause issues during cross-domain crawling.

2. CurlImpersonateHttpClient.
   Session knows nothing about cookies and all cookies are stored at the AsyncSession level. As a result, if we don't use proxies, all sessions have identical cookies. If we work with proxies, cookies become tied to the proxy.

3. Playwright.
   Session knows nothing about cookies and all cookies are stored at the PlaywrightContext level, meaning all sessions working from one context will operate with the same cookies.

[B4nan]

@Mantisus thanks for bringing this up. Let's split it into 3 separate PRs please.

[janbuchar]

Regarding 1, this will probably involve changing the Session so that it uses a more sophisticated cookie jar implementation. I'm not sure if this can be made backwards compatible...

[B4nan]

I would focus on 3 first, that feels like the biggest issue to me. Scraping multiple domains in a single crawler is not a very common use case.

[janbuchar]

I would focus on 3 first, that feels like the biggest issue to me. Scraping multiple domains in a single crawler is not a very common use case.

Agreed, even though 2. is similar in terms of severity (but yeah, playwright is a bit more popular)

[Mantisus]

2 of 3. But for multi-domain cookie support, we'd really have to go to something like http.cookiejar.CookieJar instead of dict.