Transaction ID not correctly set on Contract input

[danielbate]

When we create a new contract input against a transaction, we always zero out the transaction ID.

fuels-ts/packages/account/src/providers/transaction-request/input.ts

Line 117 in 02503a6

txID: ZeroBytes32,

This has not been a problem because this value is meant to be zeroed out for hashing/signing.

However when building out a transaction summary from a transaction response (transactionResponse.getTransactionSummary()) the summary is technically not correct as this input has not been populated correctly. Whereas a summary generated using a transaction ID (getTransactionSummary(txId)) fetches the full tx from the node, has this input set correctly.

[Torres-ssf]

I believe this happens because we no longer fetch the transaction within TransactionResponse when a transaction request is given during its instantiation.

Instead, we update specific parts of it using data from the subscription result.

cc @nedsalk

[danielbate]

Once this has been completed, we should enable the tests in #3710.