[congress] Transition Stein to EM

This transition the stein branch to extended maintenance.
Changes for bugfixes and things the team deems important are
still encouraged, but there will no longer be official releases
off of the branch.

Please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final backports currently in
flight that we should wait for. For the latter case, please
update the patch with the new commit hash after doing a final
release to get those changes out so we know to proceed with the
transition.

Change-Id: Icc7a6e51d461c73494783d9015d03e6f003cb2a0

deliverables/stein/congress-dashboard.yaml

@@ -16,6 +16,10 @@ releases:
       - hash: e5c562c7b3cab096d6b46d353a836bf71044917a
         repo: openstack/congress-dashboard
     version: 4.0.0
+  - version: stein-em
+    projects:
+      - repo: openstack/congress-dashboard
+        hash: e5c562c7b3cab096d6b46d353a836bf71044917a
 branches:
   - location: 4.0.0.0rc1
     name: stable/stein

deliverables/stein/congress.yaml

@@ -20,6 +20,10 @@ releases:
       - hash: 4977fe3dacbf4de25e8568141d9bdbf7363a5288
         repo: openstack/congress
     version: 9.0.0
+  - version: stein-em
+    projects:
+      - repo: openstack/congress
+        hash: 4977fe3dacbf4de25e8568141d9bdbf7363a5288
 branches:
   - location: 9.0.0.0rc1
     name: stable/stein

deliverables/stein/python-congressclient.yaml

@@ -9,6 +9,10 @@ releases:
     projects:
       - repo: openstack/python-congressclient
         hash: b7044328112bdeda1b7bc36da1e5c8f863b3c72a
+  - version: stein-em
+    projects:
+      - repo: openstack/python-congressclient
+        hash: b7044328112bdeda1b7bc36da1e5c8f863b3c72a
 repository-settings:
   openstack/python-congressclient: {}
 branches: