Ensure undecodable logs no longer throw an error on program calls #3932
Description
Summary
The scenario is:
-
Have an upgradable contract
-
Upgrade the contract and change only its logs
-
Send a transaction to the contract that succeeds, using the old ABI
-
The SDK will throw, because even if the transaction was successful, it could not decode some of the logs
FuelError: Log type with logId '14177907664807608982' doesn't exist in the ABI.
The transaction succeeds, but the SDK throws an error due to unknown logs.
Expected
The behaviour I would expect is that the SDK does not throw, and the logs appear empty or in some raw format. The current behaviour might be intentional, but to me it is counterintuitive because it leads me to think that there is something wrong with the transaction itself