We have decided to remove I2P (Refs: #11276) due to our failure of
finding someone interested in maintaining it in Tails.

Will-fix: #12263

Test suite: start adjusting for the way additional settings are handled in the new Greeter (refs: #12055).

In a wide variety of situation the exact timings are very important, so
this information has quite general usefulness.

... after logging in via Tails Greeter. Now we do some very important
stuff there, like enabling the accessibility toolkit in GNOME. That is
specifically something we lose if we forgot to run that step after
rebooting, which specifically was a problem in at least one scenario
(Deleting a Tails persistent partition).

While we're at it, let's also run the 'Tails Greeter has dealt with
the sudo password' step at the same time.

Hopefully a test writer would think twice before re-using this name
when creating a new disk, so we won't repeat #10907.

Refs: #10907

(yay 6094!)

Essentially I did:

    sed -i 's/Tails has booted/I have started Tails/' -- \
        features/*.feature features/step_definitions/snapshots.rb

(although there was a false positive that I had to restore)

This reverts commit e13ee256.

In the 'I enable Microsoft Windows camouflage' step we set @theme, but
it will only be set for a scenario where the checkpoint is created
(e.g. the first one run that uses it). To store such variables along
with the checkpoints we need #5847, so until then we cannot do
this. (Note that with the old system we could do this because we could
set it before the skip instruction in the step.)

Conflicts:
	features/step_definitions/snapshots.rb

... and use that facility instead (of some custom crap) for our
checkpoint creation logging.

Instead of pollutin STDERR.

It was added by a copy-paste mistake. Apparently I didn't test what I
pushed. Oops.

This test requires an iso built within the branch from #10185 merged in.

If we save the snapshot after I2P has already been started, by this
point I2P will have fetched its "RIs" (router infos) from the reseed
(bootstrap) servers. Doing it this way it should be much quicker for I2P
to bootstrap on the network and it should also help with making the I2P
tests more robust.

They're only used in one feature each, respectively.

Most of the time when testing persistence, this is what we need so it
will save some time and make the scenarios simpler.

This is just simpler than having to type it everywhere as a step
parameter.

* Always run post_snapshot_restore_hook after *saving* and *restoring*
  a snapshot. We should only need it when restoring, but when we save
  memory state only snapshots there's a built-in snapshot restore.

* Fix checkpoint creation output, and colorize it like cucumber does.

* Programatically generate steps with nice names for reaching all
  snapshots.