[vitrage] create pike-em tag against final releases

This is a procedural review to transition pike into extended maintenance by
creating the pike-em tag

It's possible that the release isn't needed (for example if there are no code
changes sine the previous release, sadly that's non-trivial to detect en masse.

If you are the PTL or release liaison for this team please +1 this review
if it is ready or -1 and take over the review to correct mistakes.

Change-Id: If990bb9d1fe180ecdc44b63aa7f982fd446f7497

deliverables/pike/python-vitrageclient.yaml

@@ -23,6 +23,10 @@ releases:
       - hash: 157ef21a5070d4dadb26977aff76a6b3dd9e32b1
         repo: openstack/python-vitrageclient
     version: 1.4.1
+  - projects:
+      - hash: 157ef21a5070d4dadb26977aff76a6b3dd9e32b1
+        repo: openstack/python-vitrageclient
+    version: pike-em
 team: vitrage
 type: library
 repository-settings:

deliverables/pike/vitrage-dashboard.yaml

@@ -24,5 +24,9 @@ releases:
       - hash: ba55c2431e54a22bf4ce4fabc9cf9dede9ca861d
         repo: openstack/vitrage-dashboard
     version: 1.3.2
+  - projects:
+      - hash: ba55c2431e54a22bf4ce4fabc9cf9dede9ca861d
+        repo: openstack/vitrage-dashboard
+    version: pike-em
 repository-settings:
   openstack/vitrage-dashboard: {}

deliverables/pike/vitrage.yaml

@@ -33,5 +33,9 @@ releases:
       - hash: c3e081d8861738e86279a8c3c872d343efe35dc5
         repo: openstack/vitrage
     version: 1.8.3
+  - projects:
+      - hash: c3e081d8861738e86279a8c3c872d343efe35dc5
+        repo: openstack/vitrage
+    version: pike-em
 repository-settings:
   openstack/vitrage: {}