Trace logging

[joshuajbouw]

As per previous discussions in #356 (comment), we require logging in the Engine which we will be able to utilise to print out logs not just through NEAR logging, but also straight to console or a file for the standalone.

Per discussion with @andrcmdr, he had mentioned that this tracing crate is superior to the log crate mentioned in the discussions. I do agree, it will give us more details than the log crate.

Right now, we only support logging to NEAR. We need to also log through other methods which is useful for the standalone.

Logs should be done anytime an event has taken place. For example, if someone calls a function, we should return a log who had called that function.

Additionally, it would be worth it to see if logs that are emitted could possibly be captured and turned into NEAR logs. That would be a better instead of the current framework we have now which checks for which feature is enabled, and uses that logging method.

[birchmd]

Note the additional place to use logging: #379 (comment)