Make the `HttpClient` interface more compatible with `fetch`

[janbuchar]

• the current state is modelled after got-scraping for backward compatibility
• get rid of HttpRequest.responseType , add .json method instead
  • maybe a .stream one as well?
• make sure that redirection, cookies and status code handling is done in Crawlee and not in the client implementation
  • this will simplify writing custom http clients

[vladfrangu]

Personally, for v4 imo we should move towards returning Request/Response-compatible objects (so fetch becomes native, undici.request can be easily adapted ala https://github.com/discordjs/discord.js/blob/a7f711b30f3089a155a0ee721e2eff511d4759fb/packages/rest/src/strategies/undiciRequest.ts#L10-L37, and everything else can just write its own adapter). What do you think 👀

[janbuchar]

Personally, for v4 imo we should move towards returning Request/Response-compatible objects (so fetch becomes native, undici.request can be easily adapted ala https://github.com/discordjs/discord.js/blob/a7f711b30f3089a155a0ee721e2eff511d4759fb/packages/rest/src/strategies/undiciRequest.ts#L10-L37, and everything else can just write its own adapter). What do you think 👀

Yeah, that's pretty much what I meant with the issue 🙂