fix tested and confirmed with GnuPG 2.5.12 on windows 10

i've included logfiles for gpg-agent and scdaemon with debug-level 10. the files include

the web client received some changes in the meantime and behaves more verbose regarding connections to a native client. we should check this again, especially if GpgOL/Web is supposed to be used for different outöook accounts at the same time.

in the meantime we decided it's not always desirable to have the process autostarted. therefore the current default (manual start) is considered ok, but if possible a configuration option should be implemented, so users can activate autostart if they find it useful.

In T2169#196673, @werner wrote:

Shall we handle this with additional retry prompts, w/o a timeout? I think this makes sense because creating keys with a backup file and a passphrase is a manual task anyway.

FWIW: as mentioned in T7452#195891, it might be necessary to manually copy the uninstaller to a temporary directory ({{ tmp_uninstall_exe }}) and call it from there to get a clean uninstall:

In T7452#195845, @aheinecke wrote:

I doubt it as what Gpg4win does here is completely standard. So the win_package module should handle it or there would be multiple results if you search for "NSIS uninstall ansible"

In T7452#195836, @aheinecke wrote:

To workaround you need to copy the uninstaller to a temporary locationm firs and then execute and delete the copy.