Handle chain with a high number of UTXO

### Describe the problem you discovered

Currently when the validation of a transaction starts, the validation nodes request the entire list of inputs of the chain.
But it is possible that the chain has a huge number of inputs and this could use too much memory and download to much data to be efficient.

### Describe the solution you'd like

We should handle chain with a lot of UTXO maybe by requesting only the required UTXO or have a limit of the number of UTXO used during the validation

### Epic

_No response_

No files, tests, or entry points are named. Start by tracing transaction validation and how validation nodes retrieve the full chain input list, then determine whether fetching only required UTXOs or imposing a validation limit can meet the memory and download goals.

Written by the indexing model from the issue text.