tests/test-batching.py.out

run-tests: stop ignoring venv-installed packages

This will allow test dependencies to be installed within a venv, instead of
tampering with sys/user sites.  One thing to note here is that the `VIRTUAL_ENV`
path takes precedence over system-site, unlike when run directly with an
activated `venv`.  For example, `sys.path` as viewed from a feature test in
`hghave.py`, when running `hghave vcr` directly with an activated `venv`:

    sys.path: [
        '/home/jenkins/hg-committed/tests',
        '/usr/lib/python38.zip',
        '/usr/lib/python3.8',
        '/usr/lib/python3.8/lib-dynload',
        '/home/jenkins/test_venv/lib/python3.8/site-packages'
    ]

vs `sys.path` from the same feature test, when run by `run-tests.py` with this
change:

    sys.path: [
        '/home/jenkins/hg-committed/tests',
        '/home/jenkins/hg-committed',
        '/home/jenkins/hg-committed/tests',
        '/home/jenkins/test_venv/lib/python3.8/site-packages',
        '/usr/lib/python38.zip',
        '/usr/lib/python3.8',
        '/usr/lib/python3.8/lib-dynload',
        '/home/jenkins/.local/lib/python3.8/site-packages',
        '/usr/local/lib/python3.8/dist-packages',
        '/usr/lib/python3/dist-packages'
    ]

== Local
Ready.
Un and Deux
Eins und Zwei
One and Two
Eins und Zwei
Uno und Due

== Remote
Ready.
REQ: foo?one=Vo&two=Efvy
  -> Vo!boe!Efvy
Un and Deux
REQ: bar?b=Fjot&a=[xfj
  -> Fjot!voe![xfj
Eins und Zwei
REQ: batch?cmds=foo:one=Pof,two=Uxp;bar:b=Fjot,a=[xfj;bar:b=Vop,a=Evf
  -> Pof!boe!Uxp;Fjot!voe![xfj;Vop!voe!Evf
One and Two
Eins und Zwei
Uno und Due