Refactor transaction entity and table to match sources
Transactions are stored as transaction document, but some fields like amount and base are a sum of the outputs.
To match each source with an transaction output, we need to split transactions by output.
For example, a transaction from Alice to Bob sending 100 to Bob, from a source of 1000, will have two outputs.
So, instead of having only one transaction in the table, we will have two.
Many fields stay the same, except
We need to simulate all use case to see what entries we can ignore...
This system will allow to display money back if inputs is greater than output. So if we allow this display we can choose it as source if we want!