Translate Python-based tests to C

This simplifies bootstrapping: now you don't have to build dbus,
build dbus-python (with GLib), and use dbus-python to test dbus.

It also avoids test failures when using facilities like
AddressSanitizer. When libdbus is built with AddressSanitizer, but the
system copies of Python and dbus-python were not, dbus-python will exit
the Python interpreter on load, because libasan wasn't already
initialized. The simplest way to avoid this is to not use Python:
the scripts are not *that* hard to translate into C.

Both of these tests happen to be conditionally compiled for Unix only.
test_activation_forking() relies on code in TestSuiteForkingEchoService
that calls fork(), which can only work on Unix; meanwhile,
test_system_signals() tests the system bus configuration, which is
only relevant to Unix because we don't support using dbus-daemon as
a privilege boundary on Windows (and in any case D-Bus is not a Windows
OS feature, so the system bus cannot be used to communicate with OS
services like it can on most Linux systems).

This is also a partial solution to
<dbus/dbus#135>, by reducing the
size of name-test/.

For this to work, we need to build the test-service helper executable
even if embedded tests are disabled.

Signed-off-by: Simon McVittie <smcv@collabora.com>
12 jobs for unpythonize in 0 seconds (queued for 77 minutes and 42 seconds)
Status Job ID Name Coverage
  Build
failed #55537
build:cmake

failed #55534
build:debug

manual #55539
allowed to fail manual
build:i686-w64-mingw32-cmake
failed #55538
build:i686-w64-mingw32-debug

manual #55542
allowed to fail manual
build:jessie
manual #55536
allowed to fail manual
build:legacy
failed #55533
build:production

manual #55535
allowed to fail manual
build:reduced
manual #55544
allowed to fail manual
build:trusty
failed #55540
build:x86_64-w64-mingw32

failed #55541
build:x86_64-w64-mingw32-cmake-debug

manual #55543
allowed to fail manual
build:xenial
 
Name Stage Failure
failed
build:x86_64-w64-mingw32-cmake-debug Build There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
build:x86_64-w64-mingw32 Build There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
build:i686-w64-mingw32-debug Build There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
build:cmake Build There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
build:debug Build There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
build:production Build There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log