Remove Zkapp_command.Wire.t

[georgeee]

This PR removes Zkapp_command.Wire.t along with a Binable-based trick that was used in combination with Zkapp_command.Wire.t to provide serialization for Zkapp_command.t.

Motivation for the refactoring lies in the fact that in the previous version hashing code was invoked from the serialization. This is problematic in two ways:

1. It gives us very little control over the sequence of hashing
   • in the light of recent work, it's very beneficial to batch independent hashing operations
   • having hash computation buried so deep in the code means that realizing benefits of the performance improvement is practically impossible
2. Hashing relies on "signature kind" configuration
   • having hash computation buried so deep means that it's practically impossible to use the value supplied by the runtime config
   • using the value supplied by compile-time configuration induces an unnecessary inflexibility in use of built binaries, and stops us from achieving eventual goal of making all of the compile-time configuration overridable with the runtime config

Explain how you tested your changes:

• Most of the changes are pure refactoring
• Some changes modify logging format in an unsubstantial way
  • many log changes are associated with Zkapp_command.Stable.Latest.t being used instead of Zkapp_command.t in various places were an error occurs during transaction processing
  • because none of these is documented as an outside-facing feature, and is meant for supplying more fine-grained debug information via logs, this seems a safe change
• Format accepted by mina advanced verify-commands has changed, but the old format is still supported with a new optional --legacy flag

Checklist:

• Dependency versions are unchanged
  • Notify Velocity team if dependencies must change in CI
• Modified the current draft of release notes with details on what is completed or incomplete within this project
• Document code purpose, how to use it
  • Mention expected invariants, implicit constraints
• Tests were added for the new behavior
  • Document test purpose, significance of failures
  • Test names should reflect their purpose
• All tests pass (CI will check this if you didn't)
• Serialized types are in stable-versioned modules
• Does this close issues? None

[georgeee]

!ci-build-me