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 行为。