[barbican] 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: Id25d26ef0b7ab117a2e006f9995b4e06cdfe16a2

deliverables/pike/barbican.yaml

@@ -30,6 +30,10 @@ releases:
       - hash: 5e756a70861e66ee52b7b20d00fc9607ad21d133
         repo: openstack/barbican
     version: 5.0.1
+  - projects:
+      - hash: 5e756a70861e66ee52b7b20d00fc9607ad21d133
+        repo: openstack/barbican
+    version: pike-em
 branches:
   - location: 5.0.0.0rc1
     name: stable/pike

deliverables/pike/python-barbicanclient.yaml

@@ -28,6 +28,10 @@ releases:
       - hash: 9f6dcb0617217241ea4260bd421b19dde35160b5
         repo: openstack/python-barbicanclient
     version: 4.5.3
+  - projects:
+      - hash: 9f6dcb0617217241ea4260bd421b19dde35160b5
+        repo: openstack/python-barbicanclient
+    version: pike-em
 branches:
   - location: 4.5.2
     name: stable/pike