Make RESUME monitoring more readable and robust

We make the code for the monitoring of PY_START and PY_RESUME events
triggered by the RESUME opcode more readable and maintainable by
not relying on some obscure logic on the value of oparg that can
easily break if the event IDs are ever changed in the future.

Author: P403n1x87

Python/bytecodes.c

@@ -240,7 +240,7 @@ dummy_func(
 
         op(_MONITOR_RESUME, (--)) {
             int err = _Py_call_instrumentation(
-                    tstate, oparg > 0, frame, this_instr);
+                    tstate, oparg == 0 ? PY_MONITORING_EVENT_PY_START : PY_MONITORING_EVENT_PY_RESUME, frame, this_instr);
             ERROR_IF(err);
             if (frame->instr_ptr != this_instr) {
                 /* Instrumentation has jumped */