[FIX]: safe_eval’ing some large scripts yield illegal opcodes

Following the 3.6 wordcode change, EXTENDED_ARGS gets used for jumps
offset by more than 256 bytes (128 opcodes), most commonly
absolute (so many script of more than 128 opcodes with conditionals
arer going to trigger the issue).

In bytecoded Python versions, EXTENDED_ARGS was only necessary above
65k opcodes: the opcode would get a separate 16-bits argument, while
wordcode opcodes get 8-bit intrinsic.

odoo/tools/safe_eval.py

@@ -96,6 +96,7 @@ _SAFE_OPCODES = _EXPR_OPCODES.union(set(opmap[x] for x in [
     'POP_BLOCK', 'POP_EXCEPT', # Seems to be a special-case of POP_BLOCK for P3
     'SETUP_LOOP', 'BREAK_LOOP', 'CONTINUE_LOOP',
     'MAKE_FUNCTION', 'CALL_FUNCTION',
+    'EXTENDED_ARG',  # P3.6 for long jump offsets.
     # P3: https://bugs.python.org/issue27213
     'CALL_FUNCTION_EX',
     # Already in P2 but apparently the first one is used more aggressively in P3