CFG (Control Flow Graph) extensions for state variables

[0x19]

Lets take real challenge I'm facing now.

In order to properly parse storage values and feed them into the state variables, THERE HAS TO BE ORDER. When contract is deployed, state variables can be reached from the storageAt() however, they are added in order of execution into the EVM and thus, they have to be fetched out from the EVM in order.

Taking for example different ways we can bring source code into the parser, it's obvious that code won't be always in order and we need to sort that out.

In order to resolve it once for good, we need to ensure that CFG is used here as we can map execution on the right way. In addition to that, CFG will later on be used for discovering vulnerabilities to one day replace slither.

Basically, this is a huge thing and it's blocking #142 to be released into the wild.

[0x19]

Code waiting for new PR in #140