Bump timeout for controlplane phases

Exceeding the timeout (2000s) for controlplane phase is one
of the common reasons of failure gate-script runner job. The new executor
with bumped timeout value was created for controlplane-* phases to help avoid
timeout error. The examples of exceeding timeout error can be found here:

[1] https://zuul.opendev.org/t/openstack/build/b26d02fda3ab4e75938bd397c618a411
[2] https://zuul.opendev.org/t/openstack/build/73ae850e150c4ce18a1153cc352cebfc
[3] https://zuul.opendev.org/t/openstack/build/7683f126b5274eb492d00d80c73c4bbb

Change-Id: I77055e25c58a4103cdbd67b09710e22829e127a0
Signed-off-by: Ruslan Aliev <raliev@mirantis.com>

manifests/phases/executors.yaml

@@ -11,6 +11,18 @@ config:
   pruneOptions:
     prune: false
 ---
+apiVersion: airshipit.org/v1alpha1
+kind: KubernetesApply
+metadata:
+  labels:
+    airshipit.org/deploy-k8s: "false"
+  name: kubernetes-apply-controlplane
+config:
+  waitOptions:
+    timeout: 3600
+  pruneOptions:
+    prune: false
+---
 # This is added to support phase with no-wait
 # When there is a wait, then it does status-check and fails
 # if the resource status(condition) is not met.

manifests/phases/phases.yaml

@@ -42,7 +42,7 @@ config:
   executorRef:
     apiVersion: airshipit.org/v1alpha1
     kind: KubernetesApply
-    name: kubernetes-apply
+    name: kubernetes-apply-controlplane
   documentEntryPoint: ephemeral/controlplane
 ---
 apiVersion: airshipit.org/v1alpha1
@@ -80,7 +80,7 @@ config:
   executorRef:
     apiVersion: airshipit.org/v1alpha1
     kind: KubernetesApply
-    name: kubernetes-apply
+    name: kubernetes-apply-controlplane
   documentEntryPoint: target/controlplane
 ---
 apiVersion: airshipit.org/v1alpha1

tools/deployment/30_deploy_controlplane.sh

@@ -30,7 +30,7 @@ do
 done
 
 echo "Create target k8s cluster resources"
-airshipctl phase run controlplane-ephemeral --debug
+time airshipctl phase run controlplane-ephemeral --debug
 
 echo "List all nodes in target cluster"
 kubectl \