Invisible reCaptcha

[mekarpeles]

We use recaptcha in a number of places throughout the site. archive.org uses an Invisible recatpcha, which does not prompt the user unless it detect suspicious activity -- we've decided to follow suit.

https://developers.google.com/recaptcha/docs/invisible

Checklist

1. The invisible reCAPTCHA requires new keys, so we'll need a new entry in openlibrary.yml for the keys. Name the new entry plugin_invisible_recaptcha, and model the entry after the existing plugin_recaptcha entry (with empty strings as the key values).
2. Update the registration form handler to use the new keys. These keys are set in the get_recap function, here.
3. Make the following updates to the account registration template (here):

• Remove the existing reCAPTCHA, and related copy
• Add the g-recaptcha class to the submit button
• Add data-sitekey to the submit button. If the form has a reCAPTCHA, use the new public key as the value. Otherwise, use an empty string.

4. Update the existing submission button click handler, here, to programmatically invoke the reCAPTCHA challenge. Form submission should not be triggered if the challenge was failed.

[imlakshay08]

Hey @mekarpeles , could you assign this task to me please? I would like to work on this issue.