…the bytecode (pythonGH-136525)Previously, we assumed that instrumentation would happen for all copies ofthe bytecode if the instrumentation version on the code object didn't matchthe per-interpreter instrumentation version. That assumption was incorrect:instrumentation will exit early if there are no new "events," even if thereis an instrumentation version mismatch.To fix this, include the instrumented opcodes when creating new copies ofthe bytecode, rather than replacing them with their uninstrumented variants.I don't think we have to worry about races between instrumentation and creatingnew copies of the bytecode: instrumentation and new bytecode creation cannot happenconcurrently. Instrumentation requires that either the world is stopped or thecode object's per-object lock is held and new bytecode creation requires holdingthe code object's per-object lock.(cherry picked from commitd995922)Co-authored-by: mpage <mpage@meta.com>