Distinguish contract execution failures from failed transactions

[cuevasm]

Lemme explain. Folks get confused why they have to pay a fee when the Explorer shows the transaction 'failed'. In reality, the transactions were mined and didn't 'fail', what failed was the contract execution. Lately, this is because all the NFTs are gone and the contract can't mint a new one and thus 'fails'. I am wondering if we can better differentiate between the two failure states so that people don't think they're paying for transactions that 'didn't go through'. They went through (and I think it's important for people to know the blockchain isn't just dropping transactions), the transcation just didn't generate the result desired.

[fbwoolf]

@cuevasm can you provide a link to an example tx in the explorer and maybe screens shots of what specifically you think needs changed? We are reading data from the api and applying the failed status to transactions that have a tx_status equal to abort_by_response or abort_by_post_condition. The Failed status in the summary section is accurate bc that is the contract execution result.