[winstackers] 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: Ibccee22563d8cc0ed6e84eb35c1ee51f5090442c

deliverables/pike/networking-hyperv.yaml

@@ -16,6 +16,10 @@ releases:
       - hash: e38a2356b43e06aee7cb9f19e2ff51273abee87d
         repo: openstack/networking-hyperv
     version: 5.0.1
+  - projects:
+      - hash: e38a2356b43e06aee7cb9f19e2ff51273abee87d
+        repo: openstack/networking-hyperv
+    version: pike-em
 release-notes: https://docs.openstack.org/releasenotes/networking-hyperv/pike.html
 repository-settings:
   openstack/networking-hyperv: {}

deliverables/pike/os-win.yaml

@@ -25,6 +25,10 @@ releases:
       - hash: 22f35e9ce7b734d4f8f930147c9e257f3506f616
         repo: openstack/os-win
     version: 2.2.1
+  - projects:
+      - hash: 22f35e9ce7b734d4f8f930147c9e257f3506f616
+        repo: openstack/os-win
+    version: pike-em
 branches:
   - name: stable/pike
     location: 2.1.0