Getting rid of `_noop.noop()` to make winloop run smoother and hacking in a special Eval Method instead.

I see why _noop.noop is in here but with no way to improve upon this function I see no reason to continue using it unless someone would like to explain it's use to me. I see a reason to rehack in _PyEvalFrameDefault even though it was removed a couple years ago from external use. All I see noop as is a new can of worms and a bottleneck. And with my desire to make winloop sharper and smoother on all ends, this stands as a current road bump in allowing this library to evolve.

cdef inline _ceval_process_signals(self):
        # Invoke CPython eval loop to let process signals.
        PyErr_CheckSignals()

        # Calling a pure-Python function will invoke
        # _PyEval_EvalFrameDefault which will process
        # pending signal callbacks.
       _noop.noop()  # Might raise ^C

I Propose taking a different approach instead of our current one.