docs: fix syntax highlighting on shell commands

Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27010>

docs/ci/bare-metal.rst

@@ -138,7 +138,7 @@ Setup
 Each board will be registered in freedesktop.org GitLab.  You'll want
 something like this to register a fastboot board:
 
-.. code-block:: console
+.. code-block:: sh
 
    sudo gitlab-runner register \
         --url https://gitlab.freedesktop.org \
@@ -194,7 +194,7 @@ Caching downloads
 To improve the runtime for downloading traces during traces job runs, you will
 want a pass-through HTTP cache.  On your runner box, install nginx:
 
-.. code-block:: console
+.. code-block:: sh
 
    sudo apt install nginx libnginx-mod-http-lua
 
@@ -213,7 +213,7 @@ your devices are on.
 
 Enable the site and restart nginx:
 
-.. code-block:: console
+.. code-block:: sh
 
    sudo rm /etc/nginx/sites-enabled/default
    sudo ln -s /etc/nginx/sites-available/fdo-cache /etc/nginx/sites-enabled/fdo-cache

docs/ci/index.rst

@@ -64,13 +64,13 @@ Farm management
 
 When the farm starts failing for any reason (power, network, out-of-space), it needs to be disabled by pushing separate MR with
 
-.. code-block:: console
+.. code-block:: sh
 
    git mv .ci-farms{,-disabled}/$farm_name
 
 After farm restore functionality can be enabled by pushing a new merge request, which contains
 
-.. code-block:: console
+.. code-block:: sh
 
    git mv .ci-farms{-disabled,}/$farm_name
 
@@ -279,7 +279,7 @@ command`` instead of ``run -it $IMAGE bash`` (which you may also find
 useful for debug).  Extract your build setup variables from
 .gitlab-ci.yml and run the CI meson build script:
 
-.. code-block:: console
+.. code-block:: sh
 
    IMAGE=registry.freedesktop.org/anholt/mesa/debian/android_build:2020-09-11
    sudo docker pull $IMAGE
@@ -288,7 +288,7 @@ useful for debug).  Extract your build setup variables from
 All you have left over from the build is its output, and a _build
 directory.  You can hack on mesa and iterate testing the build with:
 
-.. code-block:: console
+.. code-block:: sh
 
    sudo docker run --rm -v `pwd`:/mesa $IMAGE meson compile -C /mesa/_build
 

docs/ci/local-traces.rst

@@ -12,7 +12,7 @@ Running single trace
 --------------------
 A simple run to see the output of the trace can be done with
 
-.. code-block:: console
+.. code-block:: sh
 
    apitrace replay -w name_of_trace.trace
 
@@ -20,7 +20,7 @@ For more information, look into the `Apitrace documentation <https://github.com/
 
 For comparing checksums use:
 
-.. code-block:: console
+.. code-block:: sh
 
    cd piglit/replayer
    export PIGLIT_SOURCE_DIR="../"
@@ -34,7 +34,7 @@ Sometimes it's useful to be able to test traces on your local machine instead of
 
 Download the YAML file from your driver's ``ci/`` directory and then change the path in the YAML file from local proxy or MinIO to the local directory (url-like format ``file://``)
 
-.. code-block:: console
+.. code-block:: sh
 
    # The PIGLIT_REPLAY_DEVICE_NAME has to match name in the YAML file.
    export PIGLIT_REPLAY_DEVICE_NAME='your_device_name'