[congress] 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: Iea97c3534df7d73d2666c4765dfc50eb4c99f306

deliverables/pike/congress-dashboard.yaml

@@ -25,6 +25,10 @@ releases:
       - hash: e06651e2023ef50ef827ca8b94429b79866b1b92
         repo: openstack/congress-dashboard
     version: 1.0.1
+  - projects:
+      - hash: e06651e2023ef50ef827ca8b94429b79866b1b92
+        repo: openstack/congress-dashboard
+    version: pike-em
 branches:
   - location: 1.0.0.0rc1
     name: stable/pike

deliverables/pike/congress.yaml

@@ -33,6 +33,11 @@ releases:
     projects:
       - repo: openstack/congress
         hash: 6e0558e6ee1169dd5cec65d49e3197eb05597d38
+  - projects:
+      - hash: 6e0558e6ee1169dd5cec65d49e3197eb05597d38
+        repo: openstack/congress
+        tarball-base: openstack-congress
+    version: pike-em
 branches:
   - location: 6.0.0.0rc1
     name: stable/pike

deliverables/pike/python-congressclient.yaml

@@ -17,6 +17,10 @@ releases:
       - hash: 5c64747b1561b48a47ddd21505b140e9fd6a6cf5
         repo: openstack/python-congressclient
     version: 1.8.1
+  - projects:
+      - hash: 5c64747b1561b48a47ddd21505b140e9fd6a6cf5
+        repo: openstack/python-congressclient
+    version: pike-em
 branches:
   - name: stable/pike
     location: 1.8.0