ci/linux: split normal testing from valgrind testing

A test case failure usually also triggers valgrind leaks, sifting through those
to find the actual test failure is painful. So let's separate the tests and run
them separately.

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

.github/workflows/linux.yml

@@ -36,5 +36,8 @@ jobs:
         run: |
           meson compile -C build
       - name: Test
+        run:
+          meson test -C build --print-errorlogs --no-suite python-tests
+      - name: Test with valgrind
         run:
           meson test -C build --print-errorlogs --setup=valgrind --no-suite python-tests