[designate] 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: I2510245f91ed83b6ebfed6b9501c1d87426fc5a7

deliverables/pike/designate-dashboard.yaml

@@ -30,6 +30,10 @@ releases:
       - hash: 2f0ad3b4cc582130efcc02d7a00bb567ebc8ad4d
         repo: openstack/designate-dashboard
     version: 5.0.2
+  - projects:
+      - hash: 2f0ad3b4cc582130efcc02d7a00bb567ebc8ad4d
+        repo: openstack/designate-dashboard
+    version: pike-em
 branches:
   - location: 5.0.0.0rc1
     name: stable/pike

deliverables/pike/designate.yaml

@@ -35,6 +35,10 @@ releases:
       - hash: af4fc94034d5a2153e29f7584944858515d55cdb
         repo: openstack/designate
     version: 5.0.3
+  - projects:
+      - hash: af4fc94034d5a2153e29f7584944858515d55cdb
+        repo: openstack/designate
+    version: pike-em
 branches:
   - location: 5.0.0.0rc1
     name: stable/pike

deliverables/pike/python-designateclient.yaml

@@ -13,6 +13,10 @@ releases:
       - hash: da85c37baea5ec7e37851b6b3f66119d2200a33b
         repo: openstack/python-designateclient
     version: 2.7.1
+  - projects:
+      - hash: da85c37baea5ec7e37851b6b3f66119d2200a33b
+        repo: openstack/python-designateclient
+    version: pike-em
 branches:
   - name: stable/pike
     location: 2.7.0