Track issues with external abstract interpreter from the recent `CodeInstance` refactors

[aviatesk]

This is a meta issue that tracks problems with external abstract interpreters stemming from recent CodeInstance refactorings, especially #52233 and #53219.

Currently known issues include, but might not be limited to:

• Precompilation issues (JET.jl): These issues were exposed by Use tagged CodeInstances for AbstractInterpreter caching #52233, though it’s worth noting that there hadn't been robust support for caching external compilation results before the refactors. Currently investigating and discussing these in enhance the effectiveness of the test cases introduced in #53300 #53478 and 1.11: allow external abstract interpreter compilation #53488.
• Problems with irinterp by interpreters with the may_optimize option turned off (BaseBenchmarks.jl): This is due to Refactor CodeInfo/CodeInstance separation and interfaces #53219. For more detailed discussion, see b8a0a39#commitcomment-139076159

[gbaraldi]

Related PRs/issues

• Fix --compile=all mode after CodeInstance refactor #53421
• regression in thread-safety correctness of detecting compilation finished #53432
• regression in thread-safety with data-race on mi->inInference field #53433
• regression in gc safety of debuginfo #53434
• regression in inference performance caused by CodeInstance refactor #53459

Edit: I think #53431 was also supposed to be in this list

[vtjnash]

I am not certain if this discussion ever got fixed (b8a0a39#commitcomment-139109928), but the rest did