… gate

Adds ProtocolFeature::ExecutionMetadataV4 (gated at the current stable
protocol version 85, alongside ContinuousEpochSync and friends) and wires
the runtime to emit V4 outcomes when it is active.

V4 now carries a per-action Vec<AccountContract>: one entry per action in
the receipt, set to the contract that ran for FunctionCall actions and to
AccountContract::None otherwise. This preserves contract attribution for
multi-call receipts (which ProfileDataV3 already aggregates), so indexers
and light clients can correlate each action with its contract.

Mechanics:
- ActionResult drops its standalone `profile` and `executed_contract`
  fields in favor of a single `metadata: Box<ExecutionMetadataV4>` that
  owns both the gas profile and the per-action contract list.
- apply_action tracks `executed_contract` locally and pushes exactly one
  entry to result.metadata.contracts at the end (and on every early-return
  through validation failures), so the per-action invariant holds.
- ActionResult::merge sums profiles and concatenates contracts, building
  up one entry per action across the receipt.
- function_call.rs converts the near_vm_runner ProfileDataV3 to the
  near_primitives one before merging into the receipt-level profile.
- apply_action_receipt picks V4 (move result.metadata) when the feature
  is enabled and V3 (extract profile only) otherwise.

ExecutionMetadataView's contract: Option<AccountContract> field becomes
contracts: Option<Vec<AccountContract>>, still skip_serializing_if = None
so V1..V3 RPC bytes are unchanged.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

apply_action returns a per-action ActionResult carrying a single
executed_contract: AccountContract. apply_action_receipt folds those
into ActionReceiptResult, whose executed_contracts: Vec<AccountContract>
grows by one entry per merged action — the invariant ExecutionMetadataV4
relies on. AccountContract::None is the default and covers non-FunctionCall
actions, so no Option wrapper is needed.

Receipt-scoped fields (new_receipts, validator_proposals, tokens_burnt,
subsidized_amount) only make sense on the aggregate, so they no longer
need to round-trip through every per-action ActionResult before being
cleared on error. The clear-on-error logic moves into
ActionReceiptResult::set_error, called from both the Err arm of merge
and the LackBalanceForStorageStaking post-action storage check — the
latter previously faked it by merging a synthetic ActionResult, which
would now push a stray AccountContract::None onto executed_contracts.

ActionReceiptResult uses an explicit new() rather than impl Default
since it is only constructed at one site; ActionResult keeps Default
because the action helpers in actions.rs / access_keys.rs / etc. rely
on it.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

…nCall

Deploys a global contract under a CodeHash identifier, points the user
account at it via UseGlobalContract, then calls a function on that
account. The resulting receipt's ExecutionMetadataView is asserted to
be V4 with contracts == [Some(GlobalHash(code_hash))] — the case the
new metadata variant exists to surface, where the receiver (user_account)
and the executed code (global hash) diverge.

Uses the TestLoopNode tx_deploy_global_contract / tx_use_global_contract
/ tx_call helpers so nonce + tx block hash are taken from the node.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

V4 metadata's `contracts` vector previously tracked only the executed
contract for `FunctionCall` actions, leaving every other action slot as
`AccountContract::None`. That made it impossible to tell, from the
outcome alone, whether a non-FunctionCall action ran against an account
with a contract attached.

Capture `account.contract()` at the top of `apply_action`, before any
validation runs, for every action kind. `AccountContract::None` is now
only emitted when the account did not exist (e.g. a `CreateAccount`
slot) or when the resize pad fills in unexecuted trailing slots after a
mid-receipt failure.

Mechanics:
- `ActionResult::executed_contract` → `current_contract`; populated
  unconditionally at the start of `apply_action` instead of inside the
  `FunctionCall` arm.
- `ActionReceiptResult::executed_contracts` → `current_contracts`;
  merge/concatenation logic is unchanged.
- `ExecutionMetadataV4.contracts` keeps its name (the field is the
  per-action contract list either way) but the docstring now describes
  pre-action capture semantics.

Updated `test_deploy_and_call_local_receipts` so the middle
`DeployContract` slot expects `Local(rs_hash)` (the contract present
before the replace) instead of `None`, and restructured
`test_apply_v4_metadata_pads_unexecuted_actions` to deploy a contract
before the failing action so the resize pad remains distinguishable
from a real per-action capture.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>