Recaptcha after login form, website error

I've had this module running on a site for some time now and it just started producing this error the other day.

It seems to me that it would be prudent for this module to catch and handle any type of guzzlehttp errors more gracefully, especially if it's preventing users from being able to login to their site. This error may not be a fault of this module at all. This particular cURL error could be an issue with the server environment, or a problem on Google's side, or various other things. Regardless, it does not seem acceptable from a user standpoint to just get a white page with the generic error message and have to contact the web developer to sort it out. The short term solution for the site I'm working with currently was to just disable CAPTCHA altogether on the login and password reset forms, at least in the short-term.

I think the ideal solution would be to add some configuration for what to do in case the reCAPTCHA service fails in some way that prevents it from validating the CAPTCHA in the first place. One option could be to fallback on another configured CAPTCHA, or simply ignore the CAPTCHA and just allow the form to be submitted. That way the developer can choose the most desirable behaviour for their client.

It would be even better if a test could be done against the reCAPTCHA service to determine if it's working and available and working BEFORE the form loads and displays to the user to make the user experience even smoother. Either way, regular users should not have a bad experience if there's a way to handle it gracefully and ensure the UX remains smooth.

If I have time to come up with a decent solution to this I will submit a merge request.

@teknocat thanks for your comment. I think it would make sense to create a fresh issue for these improvements, this one is not a good start, I think?

Afterwards please close this one. Thanks! :)