Cypress to drive recreation from templates

A new route "RECREATE" allows the half-way between RETRY and CREATE: It
is "retry" because historic topology is loaded. It is "create" because
a new instance is created upon "Deploy".

Following commits should modify business-code, so that:

- The expectedPostAsyncInstantiation assertion pass;

- User is navigated the Instantiation-Status page;

- The template topology will be from a designated endpoint
  "templateTopology", instead of "bulkForRetry";

- Consider the hack in `templates__instance_template.json`, where action
  is "None_Create" instead of "Create" to workaround a state-oriented
  problem in the method `extractServiceFields()`.

Issue-ID: VID-724

Change-Id: I0fc282b506a05b8161f3b3f96959493d3843c7f9
Signed-off-by: Ittay Stern <ittay.stern@att.com>

1 files changed, 8 insertions, 0 deletions

diff --git a/vid-webpack-master/src/app/drawingBoard/drawingBoard.routing.ts b/vid-webpack-master/src/app/drawingBoard/drawingBoard.routing.ts
index 0c1fa700c..6564746b7 100644
--- a/vid-webpack-master/src/app/drawingBoard/drawingBoard.routing.ts
+++ b/vid-webpack-master/src/app/drawingBoard/drawingBoard.routing.ts
@@ -27,6 +27,14 @@ export const DrawingBoardRoutes: Route[] = [
         }
       },
       {
+        path: 'RECREATE',
+        component: ServicePlanningComponent,
+        resolve: {
+          flags: FlagsResolve,
+          viewEditResolver: RetryResolver
+        }
+      },
+      {
         path: 'RETRY_EDIT',
         component: ServicePlanningComponent,
         resolve: {