Integrate @fuel-ts/logger across the stack

[maschad]

Now that we've introduced a logger to the Fuel stack, we should consider where it would add the most value and what what log levels we would like to have for various types of flows.

In general one would use an info level to trace through a process e.g.

• constructing a transaction summary
• the encoding and decoding of a transaction
• Converting a callResult to a script

We would want to log warn level logs when a consumer has set a particular configuration or chosen a particular action that could result in an error. e.g.

• deploying and interacting with a contract without awaiting execution
• doing a batch transaction which could have multiple transactions fail

We would want to log error level logs when a consumer for when a consumer encounters an error that may not be thrown as an error. An example of that is

• failure to retrieve a key when deleting an item in local storage

These scenarios are by no means exhaustive but the intention of this discussion is derive a set of scenarios which we believe would benefit from logging so that we can create an issue(s) to address them.