feat(core): check we recieve txs through P2P in assertoor

[rodrigo-o]

Motivation

After the implementation of #1129, we should be receiving transactions from p2p, to check that, this PR changes the order of execution of clients in the the assertoor simulation to stop recieving txs directly from the spammer through RPC and instead getting them from other nodes and checking this continues to work after a succesfull epoch. This PR is related to #1450

[rodrigo-o]

At an specific test I was able to check that it appears to work in the beginning, with our node publishing txs that should have received from p2p:

But later it stops, and we are the only node not publishing txs on our blocks:

Given the tx spammer check is later in the execution (after the blob tx check) the run fails. There are other runs where no txs are published by our node, even at the beginning, this could be related to the first nodes publishing a block and maybe to: #797

[rodrigo-o]

If we want also to make sure every client receive txs from the spammer i.e. we are all communicating them correctly through p2p, we need to remove this check and change the previous matrix instead like:

diff --git a/.github/config/assertoor/el-stability-check.yaml b/.github/config/assertoor/el-stability-check.yaml
index d5b43170..bb3fe148 100644
--- a/.github/config/assertoor/el-stability-check.yaml
+++ b/.github/config/assertoor/el-stability-check.yaml
@@ -23,7 +23,7 @@ tasks:
       title: "Check if EL clients are synced"
 
 - name: run_task_matrix
-  title: "Check block proposals from all client pairs"
+  title: "Check block proposals from all client pairs with txs spammed"
-  timeout: 4m
+  timeout: 5m
   configVars:
     matrixValues: "validatorPairNames"
@@ -34,15 +34,9 @@ tasks:
       name: check_consensus_block_proposals
       title: "Wait for block proposal from ${validatorPairName}"
       configVars:
+        minTransactionCount: 240
         validatorNamePattern: "validatorPairName"
 
-- name: check_consensus_block_proposals
-  title: "Check the tx spammer is working as expected for block proposal with >= 240 transactions"
-  timeout: 3m
-  config:
-    minTransactionCount: 240
-    validatorNamePattern: "[\\d]-ethrex-lighthouse"
-
 - name: run_tasks_concurrent
   title: "Check chain stability (reorgs and forks)"
   timeout: 7m

[github-actions]

The amount of lines of code in the project has not changed.

[mpaulucci]

To clarify, this PR has a failing test because there are transactions that the client is not receiving through P2P. This ticket still stands: #1450

[mpaulucci]

This might also be related to #797