Move Tier 2 interpreter out of `_PyEval_EvalFrameDefault`

See discussion starting here: https://github.com/faster-cpython/ideas/issues/631#issuecomment-1995191531

Basically, we see no real perf improvement for having the two switches inside the same function, and we have some indication that on Windows the compiler is failing to optimize this giant function. In addition, the logic for each of the interpreters is somewhat complicated due to sharing variables and labels.

This is not as simple as reverting gh-111428 (issue gh-111520), but in the abstract, that's the proposal.

The priority isn't clear, but it's probably doing before the 3.13 feature freeze.

从链接的 faster-cpython 讨论开始，然后检查 _PyEval_EvalFrameDefault 以及周围的 Tier 2 interpreter 逻辑。确定两个解释器目前如何共享变量和标签，以及需要哪些边界来将它们分离。完成的标准是：移出 Tier 2 interpreter，同时保留解释器行为，并解决所述的优化问题。