[3.11] gh-101400: Fix incorrect lineno in exception message on contin…

[corona10]

…ue/break which are not in a loop (GH-101413).

(cherry picked from commit e867c1b)

Co-authored-by: Dong-hee Na [email protected]

• Issue: Negative line number in stacktrace exception #101400

[corona10]

We need to apply slightly different patches for 3.1[0-2]
For 3.11, when considering following the code line.

cpython/Python/compile.c

Lines 2060 to 2080 in 2aa4010

	case WITH:
	case ASYNC_WITH:
	SET_LOC(c, (stmt_ty)info->fb_datum);
	ADDOP(c, POP_BLOCK);
	if (preserve_tos) {
	ADDOP_I(c, SWAP, 2);
	}
	if(!compiler_call_exit_with_nones(c)) {
	return 0;
	}
	if (info->fb_type == ASYNC_WITH) {
	ADDOP_I(c, GET_AWAITABLE, 2);
	ADDOP_LOAD_CONST(c, Py_None);
	ADD_YIELD_FROM(c, 1);
	}
	ADDOP(c, POP_TOP);
	/* The exit block should appear to execute after the
	* statement causing the unwinding, so make the unwinding
	* instruction artificial */
	UNSET_LOC(c);
	return 1;

I restore the whole compiler_unit.