console.log go brrr

[anishnaik]

This PR introduces console.log functionality for medusa. The PR must satisfy the following technical requirements:

Technical Requirements

• Be close to compatible with foundry's console.log functionality (string formatting is different)
• Support string formatting
• Logs must show up in execution traces
• Adding console.log should lead to no performance hits or excessive memory costs
• The code must not take a hit on composability

Design
The console contract is now a CheatCodeContract, aka a precompiled contract. Calling console.log(x) will invoke the associated ABI method in the precompile. The method itself actually does nothing! The reason why we can do this is because our execution tracer will be able to track that the console.log precompile was called and it has access to the input arguments provided to the function. The input arguments is really all we need to handle the rest of the functionality needed by this PR.

During the creation of an execution trace, medusa will specifically search for calls to console.log and will then attempt to parse the various inputs. The main thing that needs to happen with inputs is (a) string formatting or (b) encoding the ABI values into a string. Option (b) is trivial and was already supported. medusa will gather all the logs found in an execution trace and append it to the bottom of the trace under [Logs].

String formatting
The console.log PR also supports string formatting. Note the string formatting is effectively fmt.Sprintf(formattedString, args). Since we use golang's default string formatter, we do not fully support foundry's console.log string formatting. Identifiers such as %o or %i do not work in golang. Thus, the associated documentation for our PR should highlight these differences.