This reverts commit 75449088.

I need the test suite working to release 3.0~beta2, and it's been quite broken
on feature/stretch since the merge of test/12059-dogtail-optimizations.

refs: #12305

This reverts commit cf44cb39.

This didn't improve reliability.

The .click() method actually looks up the coordinates of the element
and then clicks those coordinates. The 'press' action directly causes
a "click" event that cannot be lost.

The affected part has been failing quite regularly on Jenkins,
presumably because the GUI isn't finished loading at the time, so the
coordinates we end up clicking on (with .click()) are the wrong ones.

We now rely on our dirmngr.conf for these things.

We don't configure a custom keyserver via Enigmail anymore.

Previously we looked for the whole line, but calling .click will
result in clicking in its middle which might be something that doesn't
give focus, e.g. the column for the message status (whether it was
read or not).

... due to try_for()'s silly semantics.

Refs: #9223

... to significantly improve Dogtail's performance by saving state and
reusing it between Dogtail commands.

This is a massive commit, and it changes the semantics of the creation
of Dogtail objects. Previously they just created the code that then
would be run once an actionable method was called (.wait, .click etc),
but now it works like in Python, that Dogtail will try to find the
graphical element upon object creation.

Will-fix: #12059

We cannot clean that email up (easily) since when we use POP3 deletions
won't affect the remote inbox, only our local one. Note that we already
test SMTP in another scenario, so no test coverage is lost,
really (unless SMTP works differently with POP3 compared to IMAP, which
I think we can assume is not the case).

Will-fix: #12006

I.e. the addon that we use to find the other ones. The "amnesia
branding" addon has been removed, so we must use something else.

This is a fixup on #11906.

Refs: #11906

The previous "Improve Gherkin" broke the moved step because it couldn't
handle the case where Icedove hasn't even been started, but now it can.

Mostly because it is trivial (all "removed" code in the diff should just
be indented into the `retry_tor` block.

The extra prompt is something we rather not have to (maybe!) deal with.

Will-fix: #6304

I.e. that IMAP is preferred and that SSL/TLS is used.

Will-fix: #6304

I'm not confident in any code checking for the absence of an addon
without having an anti-test checking that the same code can detect the
presence of some other addons -- then we might as well verify that the
list is exactly what we expect.

... which incidentally fixes the issue we've had with some outdated test
suite images for this feature, and a robustness issue in TorBirdy's
settings dialog. :)

Also, by removing the IMAP scenario, which has been broken ever since we
enabled the autoconfiguration wizard, we fix another failure -- we'll
reintroduce an updated version of it shortly.

Will-fix: #11571, #11400

It depends on check.tp.o reporting that we use Tor, but we do not when
using Chutney. When we actually add usage tests of Icedove, we'll
implicitly test this any way.