After #2417 is merged

In run_execution of LEVM when we pop a callframe for handling the execution result the name of call_frame isn't very descriptive neither there nor inside the functions that take callframe as parameter.
I think that maybe executed_call_frame would be a more reasonable name. And also, the current callframe in that context could be called parent_call_frame (or not, current_call_frame is good enough I'd say).