gh-122029: Move monitoring after method expand for CALL_KW by gaogaotiantian · Pull Request #130488 · python/cpython
Per discussion in #122029 (comment), we should monitor what really happened for C code. We expanded the possible method first for CALL, but not for CALL_KW. We should do the same for CALL_KW. We can potentially remove the temp patch in legacy tracing for unpacking methods later.
CALL_FUNCTION_EX is another story and to make the PR easy to review, we are dealing with CALL_KW only in this PR. This should be a very non-intrusive change.