[Bug] _from_v06 hardcodes tx_execution_result=0, hiding actual execution results on Bradbury

[zakaziko86]

Description

In genlayer_py/types/transactions.py:437, the _from_v06 class method hardcodes tx_execution_result=0 instead of reading it from the transaction data.

Impact

• Any code using from_transaction_data() will always show NOT_VOTED as execution result on Bradbury and Asimov testnets.
• Users cannot distinguish between successful and failed contract executions via this field.
• While get_transaction() overrides this via getTransactionAllData, the from_transaction_data() path remains broken.

Suggested Fix

Map tx_execution_result from the appropriate field in the decoded tuple. For V06, tx_data[9] is txExecutionHash and may contain the execution result.

Notes

• tx_execution_result maps to: 0 = NOT_VOTED, 1 = SUCCESS, 2 = FAILURE
• Affects all users of Bradbury/Asimov testnets using from_transaction_data()