initial implementation of bona-fide-bot

[opqdonut]

for #1523

Definition of Done / Review checklist

Reviewability

• link to issue
• consider adding screenshots for ease of review

Documentation

• update changelog if necessary
• add or update docstrings for namespaces and functions
• documentation at least for config options (i.e. docs folder)
• ADR for major architectural decisions or experiments

Testing

• complex logic is unit tested
• valuable features are integration / browser / acceptance tested automatically

Follow-up

• new tasks are created for pending or remaining tasks
• no critical TODOs left to implement

[Macroz]

Some ideas for discussion. Looks good!

[Macroz]

Should we add some protection about having just one email address? Or just use find-first to be more explicit about which to return?

[opqdonut]

could be an assertion too I guess, but it's a bit impolite if it fails only when the bot tries to do something, not when creating the workflow

[opqdonut]

added a test

[Macroz]

Yeah ideally there would be some collaboration with the form editor or you would pick the email field in the workflow/bot settings. Or this could be a report of its own, data validation sort of things. We don't have to do it now as long as the docs match the exact behavior.

[opqdonut]

We could use field ids for this btw, fetching the unique field with id "referrer-email" or something?

Of course if there are multiple forms there might be multiple fields with the same field id, but we could use the first form.