We want scenario to be atomic, and not depend on other scenarios'
side-effects. Also, we save space by making disks "temporary", so they
are removed after the scenario, and don't occupy disk space.

We actually already test all this in a "hidden" way via our snapshots,
but without these scenarios it's not communicated properly via
Gherkin.

In the original branch that removed the @old_iso tag, "this" instance
was located in a different .feature file, and it was forgotten about
during the merge/conflict resolution.

For users that keep their Tails up-to-date it's very reasonable that
their Tails release date can be ~six weeks ago. Since Tails will set
the clock to the release date if it detects a time earlier than that,
we should test at least this case.

There's little reason for keeping them separate, especially when
time_syncing.feature can't have a background any way (due to the
hardware clock scenarios) which otherwise might have been a tiny
motivation.

This step was lost when re-working this feature for #6094. It should
be used whenever we expect to use one of the pre-configured accounts,
like the orc.oftc.net one.

Some details can be gleamed from:

    * http://www.jonathanleighton.com/articles/2012/stop-test-unit-autorun/
    * https://stackoverflow.com/questions/15572257/how-to-stop-rspec-from-running-test-unit-at-the-end

Conflicts:
	features/step_definitions/unsafe_browser.rb

Merge remote-tracking branch 'origin/stable'

Fix-committed: #9897

Fix-committed: #10219

Conflicts:
	features/step_definitions/common_steps.rb
	features/step_definitions/torified_gnupg.rb
	features/step_definitions/torified_misc.rb

  - Structure sentence
  - Avoid abbreviations as e.g.
  - Avoid 'should'
  - Avoid jargon such as 'whitelisted'

  - Avoid ambiguous 'it'
  - Avoid 'should'