Unified logging currently doesn't have a log tag for deoptimization. Looking at deoptimization events might be useful for tracking down the source of a temporary application slowdown. Let's add this tag.

The log output could contain similar things to the JFR event that is fired from Deoptimization::uncommon_trap_inner -> post_deoptimization_event