CIP-113 support for programmable-token transfer/balance and construction model

## Why
CIP-113 is a strategic priority with direct compliance/adoption implications, and Rosetta currently lacks a clear programmable-token construction/query model. The team needs a first implementable slice that reduces integration risk while enabling practical exchange flows.

## What
Implement initial support for CIP-113 focused on: (1) enterprise-address-first transfer and balance flows; (2) construction-model changes needed for programmable-token spends (special input/operation abstraction, required credential/signature handling, and collateral/reference-input requirements); and (3) explicit compatibility constraints for exchange and wallet integrations.

No files, tests, or entry points are named in the issue. Start by locating the existing transfer, balance, and construction flows, then clarify the CIP-113 model and integration constraints; done requires enterprise-address-first flows, programmable-token spend handling, credential and signature requirements, collateral/reference-input support, and explicit exchange and wallet compatibility.

Written by the indexing model from the issue text.