Reduce replications call by avoiding notifying node movements chains

[ghost]

In the current scheme, during the transaction validation, we are building a node movements list to specify the rewards of the validation nodes and the involved storage nodes. However, this leads to send them the transaction to update their UTXO table and their balance.

The thing is, while this scheme is acceptable, we will end up to a lot of P2P messages and replications of the transaction which will alter the performance and the throughput of the network.
For example, if you are taking a network with 50 nodes, and if each shard is composed of 20 nodes, we will have to make 100 Replication messages just to reward the nodes, without counting the recipient and emitter storage pools.

So the idea is to drop this node_movements so you can reward nodes later from their availability using the BeaconChain aggregation from the list of summaries for all the subsets.

More details here: archethic-foundation/archethic-docs#3

This will involve:

• Change the transaction structure and database field
• Change the validation processing to avoid P2P communication
• Remove the field from the UI and Graphql API
• Remove node_movements UTXO mem table entries
• Remove the UTXO type reward

---

Epic: #306

[internet-zero]

Hey team! Please add your planning poker estimate with ZenHub @apoorv-2204 @blackode @imnik11 @roychowdhuryrohit-dev @samuel-uniris