Properly format fuels dev terminal output in a helpful way

[Dhaiwat10]

Currently, the fuels dev command outputs everything that the node outputs plus some small messages which can be easily missed.

This makes it very difficult for devs to find logs, and figure out what exactly is happening in their terminal window.

We should log out only the important details like when a tx happens, when a contract is deployed, etc. And hide the rest of the details under a --verbose flag.

[arboleya]

Hmm, I don't know about this one. The more we hide, the more we abstract. As we start deciding what logs to show on behalf of the fuel-core (instead of just piping them through), we may enter dangerous/opinionated territory.

I'd consider thinking this through and [maybe] adding suggestions on the fuel-core repo.

[Dhaiwat10]

hmm. Maybe we can just do this abstraction for create fuels then? We can hide the abstraction behind a verbose flag like I mentioned, but I think this abstraction is gonna be very helpful for people building dApps who need a good, easy-to-read feedback loop when building a fullstack dApp. Right now they see a thousand long messages which are very hard to see through and figure out what exactly happened.

Thoughts? @arboleya

[arboleya]

I believe fuel-core logs are irrelevant for the create-fuels CLI but essential for the fuels dev command.

We should not try to improve fuel-core stuff in the fuels CLI, no matter how tempting that may be.

• Create users friendly logs fuel-core#1662