Limit size of generated machine code to allow more efficient branching.

Most architectures have smaller and more efficient ways of branching to "near" locations than "far" locations.

In x86-64 a branch to a location within 2GB is smaller than to an arbitrary 64 bit location.
Likewise, in AArch64, a branch to within 1MB is a single instruction, but further branches will take more instructions.

We should limit the size of traces such that we can use more efficient branches in the generated machine code.

This will have little or no impact, as traces in release builds are unlikely to ever reach this limit, but we will to need enforce it for correctness, especially in debug builds.

未指定檔案或測試。首先定位 trace 產生以及針對 x86-64 和 AArch64 的架構特定分支發射，然後確定可以在哪裡強制執行 trace 大小限制。完成的標準是：產生的 trace 保持在預期的分支範圍內，包括 debug 建置，同時不影響正常的 release 行為。