Add instruction metering

[AlixANNERAUD]

Resolve #3927 and #2163.

[AlixANNERAUD]

Currently, there is no implementation on the AOT side since I'm not sure if this is really possible since we are dealing with compiled / native code.

Regarding the classic/fast interpreter, I'm note sure about the save/restore of the context. It seems that prev_frame is saved in exec_env and reused upon invocation. However, I'm unsure whether prev_frame alone is sufficient or if we also need to back up frame (and maybe more).

[lum1n0us]

Thank you for contributing.

I totally agree with the concept of checking the meter in HANDLE_OP_END.

However, I have reservations about this part. Clearly, running out of meter should not be equated with a normal return. It's more akin to being suspended or interrupted. Additionally, unlike a normal return, there is no return value for subsequent processing. Perhaps a special exception is needed.

Another one, When instructions_left == -1, IIUC, this signifies unlimited instructions. We should bypass the calculation to minimize performance degradation, as this check occurs after every opcode execution.