schutzbot/deploy.sh: apply podman CNI network workaround on c9s

By updating the terraform ref and using newer c9s ci-runner, we started
to hit the issue that podman is falling back to using CNI network
backend when it detects existing container images in the local container
store. This is the situation for our ci-runner images, because we are
embedding container images at build time. The solution is to explicitly
set the podman network backend to 'netavark'.

Signed-off-by: Tomáš Hozza <[email protected]>

Author: thozza

schutzbot/deploy.sh

@@ -175,7 +175,7 @@ fi
 # this in osbuild, we explicitly set the network backend to 'netavark'.
 # This is relevant only for RHEL-9 / c9s, because Fedora since F40 and el10
 # support only `netavark` backend.
-if [[ $ID == "rhel" && ${VERSION_ID%.*} == "9" ]]; then
+if [[ ($ID == "rhel" || $ID == "centos") && ${VERSION_ID%.*} == "9" ]]; then
     greenprint "containers.conf: explicitly setting network_backend to 'netavark'"
     sudo mkdir -p /etc/containers/containers.conf.d
     sudo tee /etc/containers/containers.conf.d/network_backend.conf > /dev/null << EOF