[OpenStackSDK] 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: I5a63924005952f62489b97beb8b89729152ac9bc

deliverables/pike/requestsexceptions.yaml

@@ -9,6 +9,10 @@ releases:
     projects:
       - repo: openstack-infra/requestsexceptions
         hash: d7ac0ff7ca9efcc1624aae0a2431e0a5862b069f
+  - projects:
+      - hash: d7ac0ff7ca9efcc1624aae0a2431e0a5862b069f
+        repo: openstack-infra/requestsexceptions
+    version: pike-em
 branches:
   - name: stable/pike
     location: 1.3.0

deliverables/pike/shade.yaml

@@ -34,6 +34,10 @@ releases:
       - hash: 6cef59bc1fbcab8c75458f49714aae675b04c0b4
         repo: openstack-infra/shade
     version: 1.22.3
+  - projects:
+      - hash: 6cef59bc1fbcab8c75458f49714aae675b04c0b4
+        repo: openstack-infra/shade
+    version: pike-em
 storyboard: 760
 team: OpenStackSDK
 type: library