Support recursive challenge solving

[codemanki]

Fixes issue #65

What has been done:

• Everytime CF returns any response, check it for errors, new challenge, captcha or so
• Remove manual 302 processing, use followAllRedirects flag from the request library
• BREAKING CHANGE Before this, when any error has been detected, the callback was called with an incorrect order: callback(.., body, response); instead of return callback(..., response, body);
• Some code fixes, cleanup and so

What yet to be done:

• Set a limit of recursive calls, to prevent many requests to be done
• Bump major version before releasing

[Ekliptor]

I just checked it in a loop opening some of the URLs I had problems with. Works great so far.
I think all that's needed for production is a simple counter for recursive solving (max 3?) as you already mentioned to prevent an infinite solving loop. Then this is ready for production.

[codemanki]

@codemanki thanks for giving it a try. I will soon publish this version

[codemanki]

@Ekliptor done. Could you please check it once again? Now it only allows max 3 challenges

[Ekliptor]

thanks for your very thorough work and fast responses.
I merged your update with my codebase at https://github.com/Ekliptor/apputils/blob/master/src/cloudscraper/cloudscraper.ts

We are using it in production since Monday and working great so far ;)