Modify and setup the zabbix rules and agents for the Pungi nodes

Now we have the following Pungi hosts:
- x86-64-pungi-10.almalinux.dev / x86-64-v2-pungi-10.almalinux.dev (user `soksanichenko`)
- containers:
- pungi_build_node_almalinux_10_x86_64_v2
- pungi_build_node_almalinux_10_x86_64
- services
- openvpn-client@al.service
- certbot@x86-64-pungi-10.almalinux.dev.timer
- certbot@x86-64-pungi-10.almalinux.dev.service
- certbot@x86-64-v2-pungi-10.almalinux.dev.timer
- certbot@x86-64-v2-pungi-10.almalinux.dev.service
- reposync.x86_64.10.timer
- reposync.x86_64.10.service
- reposync.x86_64_v2.10.timer
- reposync.x86_64_v2.10.service
- nginx.service
- x86-64-pungi-9.almalinux.dev (user `soksanichenko`)
- containers:
- pungi_build_node_almalinux_9_x86_64
- services
- openvpn-client@al.service
- certbot@x86-64-pungi-9.almalinux.dev.timer
- certbot@x86-64-pungi-9.almalinux.dev.service
- reposync.x86_64.9.timer
- reposync.x86_64.9.service
- nginx.service
- aarch64-pungi-10.almalinux.dev / aarch64-pungi-9.almalinux.dev (user `soksanichenko`)
- containers:
- pungi_build_node_almalinux_10_aarch64
- pungi_build_node_almalinux_9_aarch64
- services:
- openvpn-client@al.service
- certbot@aarch64-pungi-9.almalinux.dev.timer
- certbot@aarch64-pungi-9.almalinux.dev.service
- certbot@aarch64-pungi-10.almalinux.dev.timer
- certbot@aarch64-pungi-10.almalinux.dev.service
- reposync.aarch64.9.timer
- reposync.aarch64.9.service
- reposync.aarch64.10.timer
- reposync.aarch64.10.service
- nginx.service
- ppc64le-pungi-10.almalinux.dev / ppc64le-pungi-9.almalinux.dev (user `almabuilder`)
- containers:
- pungi_build_node_almalinux_9_ppc64le
- pungi_build_node_almalinux_10_ppc64le
- services:
- openvpn-client@al.service
- certbot@ppc64le-pungi-9.almalinux.dev.timer
- certbot@ppc64le-pungi-9.almalinux.dev.service
- certbot@ppc64le-pungi-10.almalinux.dev.timer
- certbot@ppc64le-pungi-10.almalinux.dev.service
- reposync.ppc64le.9.timer
- reposync.ppc64le.9.service
- reposync.ppc64le.10.timer
- reposync.ppc64le.10.service
- nginx.service
- s390x-pungi-10.almalinux.dev / s390x-pungi-9.almalinux.dev (user `almabuilder`)
- containers:
- pungi_build_node_almalinux_9_s390x
- pungi_build_node_almalinux_10_s390x
- services:
- openvpn-client@al.service
- certbot@s390x-pungi-9.almalinux.dev.timer
- certbot@s390x-pungi-9.almalinux.dev.service
- certbot@s390x-pungi-10.almalinux.dev.timer
- certbot@s390x-pungi-10.almalinux.dev.service
- reposync.s390x.9.timer
- reposync.s390x.9.service
- reposync.s390x.10.timer
- reposync.s390x.10.service
- nginx.service

We need the following rules/triggers for those items:
For the hosts
- A host availability by SSH (default port 22)
- Working Nginx service. The URL `https:///almalinux` should be accessible
- The last execution of timer `reposync...timer` should be less than day ago
- The last execution of service `reposync...service` should be successful
- Service `openvpn-client@al.service` is running and the URL `http://172.28.29.85:8080` is available on a host
For the docker containers:
- A docker container is running
- A docker container is available by SSH (ports: 6021 for AL10, 6022 for AL9)
- Process `java -jar /root/jenkins/agent.jar -jnlpUrl http://172.28.29.85:8080/computer/AL/jenkins-agent.jnlp -secret @/root/jenkins/agent.secret-file -workDir /root/jenkins` is running. There are is 9 or 10, is container’s architecture in upper case. For example `AL10S390X` or `AL10X86_64_V2`
- Check validity SSL certificate of each domain
- The last execution of timer `certbot@.timer` should be less than a month ago
- The last execution of service `certbot@.service` should be successful

All rules and agents for AL8 hosts and containers should be removed