Patch plan with type/site specific phases

* Use patch to re-define the plan definition with required
  sequence of phases applicable to the specific type/site instead of
  defining a new plan.
* The idea of this change is to have one unique plan for deployment
'deploy-gating' with its own definition per type/site.

RelatesTo: #176
Change-Id: I162883dd2e86b709fbb483b985130e8748d8e557

manifests/type/airship-core/phases/kustomization.yaml

@@ -5,6 +5,7 @@ resources:
   - ../../../function/phase-helper/
   - executors.yaml
   - phases.yaml
-  - plan.yaml
 transformers:
   - ../../../../../airshipctl/manifests/function/validator
+patchesStrategicMerge:
+  - plan-patch.yaml

manifests/type/airship-core/phases/plan-patch.yaml

@@ -1,7 +1,7 @@
 apiVersion: airshipit.org/v1alpha1
 kind: PhasePlan
 metadata:
-  name: deploy-aiship-core-gating
+  name: deploy-gating
 description: "Phase plan for airship-core deployment on gating"
 phases:
   # Deploy ephemeral node using redfish with iso

tools/deployment/airship-core/25_deploy_gating.sh

@@ -14,4 +14,4 @@
 
 set -xe
 
-airshipctl plan run deploy-aiship-core-gating --debug
+airshipctl plan run deploy-gating --debug