Add the requested fields of a transaction in P2P message

### Is your feature request related to a problem?

Actually we have multiple request that return a transaction or a list of transaction. But in some case we don't need all the transaction information but just some of them.
The problem is that if the transaction has a size of 3MB and we just need address and timestamp, we use a lot of network bandwith for nothing.

### Describe the solution you'd like

When we ask the DB for transaction data, we can pass the fields we need in parameter. We should use the same behavior for the P2P message requesting a transaction.

### Additional context

We can create a new function in `Utils` module to serialize or deserialize the requested fields.

Start by tracing the existing DB requests that accept selected transaction fields and the P2P message path for requesting transaction data. Review the Utils module and its serialization/deserialization helpers. Done means a P2P transaction request can specify fields and the response transfers and reconstructs only those requested fields.

Written by the indexing model from the issue text.