[horizon] 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: Ia14576c167c722b71ef96a6f5cabecb7028af7b7

deliverables/pike/django_openstack_auth.yaml

@@ -29,6 +29,10 @@ releases:
     projects:
       - repo: openstack/django_openstack_auth
         hash: ddcfe7a6d4db1b476254b556057756eadd7b097d
+  - projects:
+      - hash: ddcfe7a6d4db1b476254b556057756eadd7b097d
+        repo: openstack/django_openstack_auth
+    version: pike-em
 branches:
   - name: stable/pike
     location: 3.5.0

deliverables/pike/horizon.yaml

@@ -49,6 +49,10 @@ releases:
       - hash: eba87483eaea45905b4f260130f319404aa17fa5
         repo: openstack/horizon
     version: 12.0.4
+  - projects:
+      - hash: eba87483eaea45905b4f260130f319404aa17fa5
+        repo: openstack/horizon
+    version: pike-em
 branches:
   - location: 12.0.0.0rc1
     name: stable/pike