[magnum] 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: I1b8fef5d8c966ad89da712140fbea4d761675ab9

deliverables/pike/magnum-ui.yaml

@@ -15,6 +15,10 @@ releases:
       - hash: 3dc74b280a01363a64a8d3d368fcba2882ef31bd
         repo: openstack/magnum-ui
     version: 3.0.1
+  - projects:
+      - hash: 3dc74b280a01363a64a8d3d368fcba2882ef31bd
+        repo: openstack/magnum-ui
+    version: pike-em
 release-notes: https://docs.openstack.org/releasenotes/magnum-ui/pike.html
 repository-settings:
   openstack/magnum-ui: {}

deliverables/pike/magnum.yaml

@@ -20,5 +20,9 @@ releases:
       - hash: 6777ba5640b5be87fe48561f9a8a63403b7d9d95
         repo: openstack/magnum
     version: 5.0.2
+  - projects:
+      - hash: 6777ba5640b5be87fe48561f9a8a63403b7d9d95
+        repo: openstack/magnum
+    version: pike-em
 repository-settings:
   openstack/magnum: {}

deliverables/pike/python-magnumclient.yaml

@@ -17,6 +17,10 @@ releases:
       - hash: 2754b15cd4f2bf73441487a3dde526d61019849f
         repo: openstack/python-magnumclient
     version: 2.7.1
+  - projects:
+      - hash: 2754b15cd4f2bf73441487a3dde526d61019849f
+        repo: openstack/python-magnumclient
+    version: pike-em
 branches:
   - name: stable/pike
     location: 2.7.0