copr: define services_disabled per instance

AFAIK we use `services_disabled: true` only when upgrading our severs
from Fedora N to Fedora N+1 which is a big task and we go instances
one by one. Maybe the easier ones in parallel but copr-backend
requires full attention for sure.

If we set `services_disabled: true` for the whole devl/production, we
can't test if the services on each server are starting properly nor we
can't run at least the frontend until all servers are ready.

Let's configure the variable per instance, so whoever is upgrading it
can disable/enable the services when needed.

inventory/group_vars/copr_back_aws

@@ -43,3 +43,4 @@ tcp_ports: [
     # node_exporter/prometheus
     9100,
 ]
+services_disabled: false

inventory/group_vars/copr_dist_git_aws

@@ -11,3 +11,4 @@ letsencrypt:
       mail: copr-devel@lists.fedorahosted.org
   predefined_deploy_script: httpd
 tcp_ports: [22, 80, 443]
+services_disabled: false

inventory/group_vars/copr_dist_git_dev_aws

@@ -12,3 +12,4 @@ letsencrypt:
       mail: copr-devel@lists.fedorahosted.org
   predefined_deploy_script: httpd
 tcp_ports: [22, 80, 443]
+services_disabled: false

inventory/group_vars/copr_front_aws

@@ -25,3 +25,4 @@ letsencrypt:
       mail: copr-devel@lists.fedorahosted.org
   predefined_deploy_script: httpd
 tcp_ports: [22, 80, 443]
+services_disabled: false

inventory/group_vars/copr_front_dev_aws

@@ -27,3 +27,4 @@ letsencrypt:
       mail: copr-devel@lists.fedorahosted.org
   predefined_deploy_script: httpd
 tcp_ports: [22, 80, 443]
+services_disabled: false

inventory/group_vars/copr_keygen_aws

@@ -5,3 +5,4 @@ custom_rules: ['-A INPUT -p tcp -m tcp -s 52.44.175.77 --dport   80 -j ACCEPT',
 datacenter: aws
 freezes: false
 tcp_ports: [22]
+services_disabled: false

inventory/group_vars/copr_keygen_dev_aws

@@ -5,3 +5,4 @@ custom_rules: ['-A INPUT -p tcp -m tcp -s 18.208.10.131   --dport   80 -j ACCEPT
 datacenter: aws
 freezes: false
 tcp_ports: [22]
+services_disabled: false