Use mamba build rather than mamba mambabuild

Since Conda 23.7.3, the plugin mechanism changed, and mambabuild
broke.

Adapt to this change, following the fix in mamba (mamba-org/mamba#2732)

ci/build_cpp.sh

@@ -11,7 +11,8 @@ rapids-print-env
 
 rapids-logger "Begin cpp build"
 
-rapids-mamba-retry mambabuild \
+# With boa installed mamba build forward to boa
+rapids-mamba-retry build \
     conda/recipes/libcudf
 
 rapids-upload-conda-to-s3 cpp

ci/build_python.sh

@@ -15,24 +15,25 @@ CPP_CHANNEL=$(rapids-download-conda-from-s3 cpp)
 
 # TODO: Remove `--no-test` flag once importing on a CPU
 # node works correctly
-rapids-mamba-retry mambabuild \
+# With boa install mamba build forwards to the boa builder
+rapids-mamba-retry build \
   --no-test \
   --channel "${CPP_CHANNEL}" \
   conda/recipes/cudf
 
-rapids-mamba-retry mambabuild \
+rapids-mamba-retry build \
   --no-test \
   --channel "${CPP_CHANNEL}" \
   --channel "${RAPIDS_CONDA_BLD_OUTPUT_DIR}" \
   conda/recipes/dask-cudf
 
-rapids-mamba-retry mambabuild \
+rapids-mamba-retry build \
   --no-test \
   --channel "${CPP_CHANNEL}" \
   --channel "${RAPIDS_CONDA_BLD_OUTPUT_DIR}" \
   conda/recipes/cudf_kafka
 
-rapids-mamba-retry mambabuild \
+rapids-mamba-retry build \
   --no-test \
   --channel "${CPP_CHANNEL}" \
   --channel "${RAPIDS_CONDA_BLD_OUTPUT_DIR}" \