The "GnuPG uses the configured keyserver" step needs to be adjusted for Stretch
We now use GnuPG v2, so network operations are delegated to dirmngr and gpg's stderr does not mention the keyserver being used.
We should instead parse the output of
gpg-connect-agent --dirmngr 'keyserver --hosttable' /bye (or similar).
And then, perhaps the ugly
gnupg_recv_key_res variable can go away :)
Meanwhile, I'm going to disable this step.
Disable the "GnuPG uses the configured keyserver" step, that needs to be updated for Stretch (refs: #12068).
Rationale: this step is a nice bonus in the "Fetching OpenPGP keys using GnuPG
should work and be done over Tor" scenario, but it should not block me from
exercising the most important part of this scenario.
Test suite: fix 'GnuPG uses the configured keyserver' step.
... after the gpg2 migration.