fix(test_committee): ensure proposal and CC members in one epoch

Moved the wait_for_epoch_interval call to ensure proposal is submitted
and CC members data created within one epoch. This change ensures that
the actions_epoch is correctly set before calculating the expiration of
new CC members.

Author: mkoura

cardano_node_tests/tests/tests_conway/test_committee.py

@@ -377,8 +377,14 @@ def test_add_rm_committee_members(  # noqa: C901
 
         [r.success() for r in (reqc.cli003, reqc.cli004, reqc.cli005, reqc.cli006)]
 
+        # Make sure we have enough time to submit the proposals in one epoch
+        clusterlib_utils.wait_for_epoch_interval(
+            cluster_obj=cluster, start=1, stop=common.EPOCH_STOP_SEC_BUFFER - 10
+        )
+        actions_epoch = cluster.g_query.get_epoch()
+
         # New CC members to be added
-        cc_member1_expire = cluster.g_query.get_epoch() + 3
+        cc_member1_expire = actions_epoch + 3
         cc_members = [
             clusterlib.CCMember(
                 epoch=cc_member1_expire,
@@ -707,12 +713,6 @@ def _check_resign_dbsync(res_member: clusterlib.CCMember) -> None:
                 cc_member_cold_key=res_member.cold_vkey_hash
             )
 
-        # Make sure we have enough time to submit the proposals in one epoch
-        clusterlib_utils.wait_for_epoch_interval(
-            cluster_obj=cluster, start=1, stop=common.EPOCH_STOP_SEC_BUFFER - 10
-        )
-        actions_epoch = cluster.g_query.get_epoch()
-
         # Create an action to add new CC members
         add_cc_action, action_add_txid, action_add_ix = _add_members()