Tier 2 trace projection does not insert necessary guards

Tier 2 trace projection can project traces through branches, calls, etc.
Currently we rely on the tier 1 instruction definition to perform the necessary checks, but this is flawed.

Consider a perfectly valid specialization of calls to class, that checked merely that the callable was a class.
This would be a perfectly valid instruction and will work flawlessly in tier 1, but will be wrong in a tier 2 trace that assumes a specific class.
Tier 2 trace projection needs to insert the necessary guards.

A lot of these extra guards will be redundant, but we can rely on the optimizer to remove them.

定位 Tier 2 追蹤投影的進入點，並將其與 Tier 1 指令定義進行比較，重點關注分支和呼叫。定義缺少的 guard 情況，然後驗證當某個指令將 callable 特化為特定類別時，投影後的追蹤仍然正確，同時涵蓋由最佳化移除的冗餘 guard 情況。