Patch for tx_info and block_tx_info (collateral_tx_out)

[rdlrt]

Description

The outputs for collateral_tx_out are never really created on chain - and thus, any assets involved are never committed to ma_tx_out. However, current references for collateral_tx_out in tx_info and block_tx_info endpoints does an incorrect join assuming collateral_tx_out.id can be joined against ma_tx_out -> tx_out_id (latter is strictly only to be mapped against tx_out.id) . This resulted in collateral_tx_out returning inconsistent and wrong results across instances due to invalid key to join.

Which issue it fixes?

#284

How has this been tested?

Tested on local preprod instance using below (should be empty):

curl -sX POST "http://127.0.0.1:18053/api/v1/tx_info?select=collateral_output->asset_list"  -H "accept: application/json" -H "content-type: application/json"  -d '{"_tx_hashes":["6fc9e482959befc6928d2691caa62c8a52a5abce167bd5fce8874cc315bb346d"]}'
# [{"asset_list":"[]"}]

[Scitz0]

Looks ok but require schema update as the format of asset desc field doesn't match other asset outputs.