Welcome node receive wrong notification from validation nodes

### Describe the problem you discovered

In certain edge cases, a validation node might become isolated (e.g., due to network issues) and fail to communicate with other validation nodes. If so, the isolated node may trigger a validation timeout due to missing updates from the coordinator or cross-validation nodes.

When the timeout occurs, the isolated node reports a transaction timeout to the Welcome Node, which notifies the client of a timeout error. However, if other validation nodes successfully process the transaction, the transaction may still be finalized on the network. This creates a discrepancy: the client receives a false timeout error despite the transaction ultimately succeeding.

### Describe the solution you'd like

We should find a way to handle isolated node reporting wrong error to the welcome node.
A possible solution could be the following:
When the welcome node send the transaction to validation nodes, it count the number of positive response from them and if it receive validation error the welcome node should wait to have at least 2 errors if more than one validation nodes responded positively.

We should also handle this behavior when a transaction is forwarded by the welcome node

### Epic

_No response_

Start by tracing transaction handling between the Welcome Node and validation nodes, including the path for transactions forwarded by the Welcome Node. Investigate how positive responses and validation timeouts are reported, then define and test behavior for isolated nodes so a timeout is not sent when the transaction is finalized by other validation nodes.

Written by the indexing model from the issue text.