playbooks: Use the same commands as mentioned in the documentation

... at https://containertoolbx.org/install/

There are some minor benefits to always invoking meson(1), as opposed to
directly invoking the underlying build backend, like 'ninja'.

It's one less command to be aware of.  Secondly, in theory, Meson can be
used with backends other than Ninja (see 'meson configure'), even though
Ninja is the most likely option for building Toolbx because it's only
supported on Linux.

https://github.com/containers/toolbox/pull/1142

playbooks/build.yaml

@@ -1,12 +1,12 @@
 - name: Build Toolbox
-  command: ninja -C builddir
+  command: meson compile -C builddir
   args:
     chdir: '{{ zuul.project.src_dir }}'
     creates: builddir/src/toolbox
 
 - name: Install Toolbox
   become: yes
-  command: ninja -C builddir install
+  command: meson install -C builddir
   args:
     chdir: '{{ zuul.project.src_dir }}'
     creates: /usr/local/bin/toolbox

playbooks/setup-env.yaml

@@ -4,7 +4,7 @@
     - include_tasks: dependencies.yaml
 
     - name: Set up build directory
-      command: meson --fatal-meson-warnings builddir
+      command: meson setup --fatal-meson-warnings builddir
       args:
         chdir: '{{ zuul.project.src_dir }}'
 

playbooks/unit-test.yaml

@@ -2,6 +2,6 @@
 - hosts: all
   tasks:
     - name: Test
-      command: ninja -C builddir test
+      command: meson test -C builddir
       args:
         chdir: '{{ zuul.project.src_dir }}'