Streamline the `MAKE_WARM` micro-op

[markshannon]

The MAKE_WARM micro-op is inserted into every piece of jitted code and within the loop if there is one.
So it needs to be cheap.

Currently, it does this:

    current_executor->vm_data.warm = true;
    if (--tstate->interp->trace_run_counter == 0) {
        _Py_set_eval_breaker_bit(tstate, _PY_EVAL_JIT_INVALIDATE_COLD_BIT);
    }

we should move the logic for testing for "coldness" onto a less frequently taken path, perhaps in the jit itself, so _MAKE_WARM just needs to do the "warming":

    current_executor->vm_data.warm = true;

[abebus]

Hi! I’m not claiming this issue- if someone else wants to take it, I’ll step aside, since I don’t have much practice with JIT. But if no one does, I’d like to dig into it and give it a try. I find this topic very interesting, and it would be a good opportunity to get some practice and understand it better