The Enter press is necessary to make the file chooser actually select
the file -- before that no file is selected, so pressing Open does
nothing.

Sometimes Dogtail will find the button and click it before it is
shown (searchShowingOnly is not perfect) which generally means
clicking somewhere on the Terminal => the click is lost *and* the
installer does no go to the foreground. So let's wait a bit extra.

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

It happened in commit c493a5f5.

Mistakes were made in these resolutions:

* d197378c
* a3873e14

We won't have it in Tails 3.0~beta1 since the Greeter doesn't have
that option, and it's not even sure we'll reintroduce it since it's
apparently quite buggy and not widely used.

Will-fix: #12055
Refs: #12093

Now we also accept if the error is shown but for *other* devices than
the target device.

So now we can use snapshots in the affected scenarios, which this commit
also implements.

Will-fix: #5571

The retry-logic we add makes some steps awkward, especially when they
really are about verifying the results of some previous steps. Any way,
let's make the best out of it.

It's correct in the .feature file.

That error implies that the assertion must fail, so this is the required
order of things.

Tails Installer can apparently show a partition (/dev/sda1) instead of
the parent device (/dev/sda).

I have some vague hope that switching USB controllers might help with problems
we see on Jenkins when booting from USB (refs: #11588). This change requires
upgrading the machine type as well, QEMU otherwise won't boot from this USB
3.0 controller. And while we're at it, let's migrate from IDE to SATA,
in order to reflect better hardware Tails is being used with.

Also, there are chances that more recent virtual hardware sees more testing
these days, so it sounds potentially useful to "upgrade".

Note that I've initially tried the more modern pc-q35-2.5 machine type,
which worked fine when running the test suite on a sid host, but when
running on Jessie the VM under testing crashed when logging into GNOME.
I'll file a ticket about trying this again once Stretch is out.

I've seen these steps timeout on Jenkins, and giving them a little bit
more time seems to make them more robust.

Refs: #10840

Refs: #10840

I've seen this take a little bit more than 30 seconds on Jenkins.

Refs: #10840

This reverts commit 0e98e38b.

That was not the intent of this ticket.

Refs: #10840

Otherwise the step fails when UDisks maps the encrypted device with
weird characters.

Refs: #10558

Refs: #10558

Using the same trick than for the UDF downloading.

Refs: #6309

Refs: #6309

This addition tests regressions on bug #10784.

Refs: #10840

Normally we'd expect Tails to run from /dev/sda1 when installed via
the Installer, or /dev/sda4 when Tails is a isohybrid, but it seems
the latter case can be running straight from /dev/sda too, so let's
just allow that -- it's the expected device, at least. :)

Will-fix: #10504