jump, branchif, etc don't invalidate locals in the JIT; they might in the interpreter because they can execute arbitrary code, but the JIT side exits before that happens.

This can happen with documentation updates and we don't want
those to trip on ZJIT tests.

Redact the whole name since names like "_bi342" aren't that helpful
anyways.

This adds comments to the hir dump output like this:

  v13:BasicObject = SendWithoutBlock v6, :test, v11 # SendFallbackReason: Complex argument passing

ZJIT: Print local variable names GetLocal and SetLocal instructions

ZJIT: Standardize C call related insn fields

- Add `recv` field to `CCall` and `CCallWithFrame` so now all method dispatch
  related instructions have `recv` field, separate from `args` field.
  This ensures consistent pointer arithmetic when generating code for these
  instructions.
- Standardize `recv` field's display position in send related instructions.

JIT-to-JIT sends don't blit locals to nil in the callee's
EP memory region because HIR is aware of this initial state and
memory ops are only done when necessary. Previously, we
read from this initialized memory by emitting `GetLocal` in e.g. BBs
that are immediate successor to an entrypoint.

The entry points sets up the frame state properly and we also reload
locals if necessary after an operation that potentially makes the
environment escape. So, listen to the frame state when it's supposed to
be up-to-date (`!local_inval`).