[congress] Transition Rocky to EM

This transition the rocky 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: Ifb1790af883f4067a1d26c3684a86382b7ef5d7f

deliverables/rocky/congress-dashboard.yaml

@@ -30,6 +30,10 @@ releases:
       - repo: openstack/congress-dashboard
         hash: 96bfbc09b52e9548a8773917130920b284a9909e
     version: 3.0.1
+  - version: rocky-em
+    projects:
+      - repo: openstack/congress-dashboard
+        hash: 96bfbc09b52e9548a8773917130920b284a9909e
 branches:
   - location: 3.0.0.0rc1
     name: stable/rocky

deliverables/rocky/congress.yaml

@@ -29,6 +29,10 @@ releases:
       - repo: openstack/congress
         hash: e4693afce7fa318f610d11988b5d484e19f559aa
     version: 8.0.1
+  - version: rocky-em
+    projects:
+      - repo: openstack/congress
+        hash: e4693afce7fa318f610d11988b5d484e19f559aa
 branches:
   - location: 8.0.0.0rc1
     name: stable/rocky

deliverables/rocky/python-congressclient.yaml

@@ -16,5 +16,9 @@ releases:
     projects:
       - repo: openstack/python-congressclient
         hash: c7cd43b5fbb2923c802be4c04933ff8e359ddb85
+  - version: rocky-em
+    projects:
+      - repo: openstack/python-congressclient
+        hash: c7cd43b5fbb2923c802be4c04933ff8e359ddb85
 repository-settings:
   openstack/python-congressclient: {}