Honeypot against Bot registrations - #4970

Thanks for offering this PR @nesges,
I'm not too keen on playing cat-and-mouse with bots, but since a honeypot like this is quite simple I think this would be a reasonable default addition.

A couple of questions:

• Is the use of the ambrosia-container class name specific or significant in any way? I understand you need to uniquely target that section but just want to understand that in case of future changes.
• Would you be able to add a couple of Registration Test cases? Just to ensure the field is on the page, and the request is rejected on that field being filled. (extra guidance on our tests here)

The class name ambrosia-container is totally arbitrary and can easily be swapped. I just wanted to avoid naming it honeypot because I'm always overstating bot cleverness.

Will gladly look into the Test cases and add some to RegistrationTest. However, I'm just getting ready to go on vacation and not sure if I can do it at short notice

@nesges thanks for confirming on the class name.

Will gladly look into the Test cases and add some to RegistrationTest. However, I'm just getting ready to go on vacation and not sure if I can do it at short notice

Okay, don't add stress before your vacation then, I can throw these in during testing/review.
Enjoy the vacation!

That's kind of you, thanks! :-)

Thanks again @nesges, now merged for next feature release with some testing and minor tweaks made in 5c28bcf.