The ScriptProxy part was a remnant from the time when I was still
concidering supporting Dogtail's procedural API, but it's now clear
that it will be too hard and not offer anything beyond the Tree
API. Also, the `interact` + block idea was from this time, and also
from a part of rewritten Git history where each use of the Dogtail
class instance inside the? `interact` block built up a single script,
that then was executed. However, since you can mix-in other calls
(e.g. to Sikuli) that may expect that a change already has happened,
that seemed like a bad approach.

So, let's KISS and simply settle on the classes Application and Node,
roughly reflecting those classes in the Tree API. The diff might look
scary, but it just moves code around, and removes some confusing
parts.

This partially reverts commit 9d82539e.

The reason is that Dogtail (or rather the a11y/AT-SPI stack it builds
on) has issues with pinentry. E.g. accerciser simply cannot see it,
and everything else experiences a long delay => the tests take much
longer to run.

I've seen instances where `config.searchShowingOnly` is set multiple
times, which makes sense -- we add it for each component.

This will greatly speed up VM.file_{append,overwrite}() and in
particular make it much faster to transfer Dogtail scripts.

If this idea turns out working well, this should be upstreamed.

Epic simplification++

Refs: #10721

This provides a simple interface for generating python code, sending
it to the guest, and executing it.

Refs: #10721

intrigeri authored Feb 14, 2016 and anonym committed Mar 30, 2016

We have to stop manually removing python-apt, since python-dogtail Depends:
python-apt.

refs: #10721

Fix-committed: #11264

Against the one from torbrowser-launcher 0.2.4-1.

Will-Fix: #11264

Then the password is never leaked.